-
Notifications
You must be signed in to change notification settings - Fork 108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KKP: Missing Documentation for Alternative Authentication Provider Under Securing System Services #1527
Comments
Raising this issue in reference to the feedback from the https://support.kubermatic.com/a/tickets/6068 on the IAP documentation. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with /lifecycle rotten |
Rotten issues close after 30d of inactivity. /close |
@kubermatic-bot: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/remove-lifecycle rotten |
@archups: Reopened this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Reopened as this is based on customer feedback in the pending support ticket. https://support.kubermatic.com/a/tickets/6068?current_tab=details |
Alternative Authentication Provider documentation section has reference to the OIDC provider for alternative authentication provider configuration, but the information is in general missing for KKP and IAP integration with alternative authentication provider.
Rather than giving reference to the OIDC Provider configuration, it would be nice if we can elaborate it under the Alternative Authentication Provider itself.
The text was updated successfully, but these errors were encountered: