You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
That's it! As soon as the above cluster has booted, it'll announce itself and communicate its URL to the `MultiClusterWebServer`.
119
119
120
+
> ⚠️ We pulled the `apiKey` configuration out of the auto-discovery configuration. In the next release this configuration is changing from `.andAutoDiscovery("https://multi-cluster.acme.com/multi", "my-api-key", "Order fulfillment service")` to `andApiKey("my-api-key").andAutoDiscovery("https://multi-cluster.acme.com/multi", "Order fulfillment service")`.
121
+
120
122
>**Note**:if provided, the API-Key needs to be shared by both servers.
121
123
122
124
>For alternative auto-discovery configuration see the API of `JobRunrDashboardWebServerConfiguration`.
123
125
126
+
124
127
### Authentication
125
128
126
129
TheMulti-ClusterDashboard supports the same [user authentication schemes]({{< ref "guides/authentication">}}) as a regular JobRunrProDashboard. The only way to authenticate server-to-server communication is to configure shared API keys. Once configured, servers pass the key along with each request. A valid API key provides full access to all the endpoints.
0 commit comments