User feedback for unsupported IdP scenarios for an MCP

[andreaskienle]

Description

Current state

• Users can configure any number of Identity Providers (IdPs) for each MCP instance (ranging from 0 to n)
• If no IdP is configured, the Onboarding IdP is implicitly used (see https://pages.github.tools.sap/cloud-orchestration/docs/managed-control-planes/access/authentication#user-provided-identity-providers)
• At the moment our BFF does not support multiple IdPs, i.e. we can only work with the IdP of the Onboarding API.
• The current supported scenario is: either no IdP is configured, or exactly one IdP is configured and it matches the Onboarding API’s IdP.

Improvements Needed

We should probably provide clear feedback in the following scenarios:

• Multiple IdPs configured: If more than one IdP is configured, should we inform the user and clarify which IdP will be used? Should we indicate that our system currently only supports a single IdP?
• No matching IdP: If none of the configured IdPs match the IdP used by the Onboarding API, users should be notified that they cannot connect to the MCP because of this.

Example of an MCP with multiple IdPs on DEV: /mcp/projects/i541351 → my-controlplane (to access get in touch with @maximilianbraun or @andreaskienle)

Acceptance Criteria

• Show Default and Custom IDPs: On Custom, gay out and add: "Non-Default IDP not supported.
• offer click for "dwonload kubeconfig"

Out of scope

• Allow Custom IDP to be added/edited on ManagedControlPlane #148

[enrico-kaack-comp]

to use the supported system idp, the user sets spec.authentication.enableSystemIdentityProvider: true in the mcp spec. We can use this to determine if we support the idp.

I suggest to gray out the button, show a yellow warning icon that gives a tooltip or modal to explain that this configuration is not supported and only system idp is supported.

[maximilianbraun]

Maybe then you just offer a download button to the kubeconfig