Allow configuring OpenID authentication #101
Closed
Conversation
Hey frodenas! Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA. |
We have created an issue in Pivotal Tracker to manage this. Unfortunately, the Pivotal Tracker project is private so you may be unable to view the contents of the story. The labels on this github issue will be updated when the story is started. |
We need to discuss this with the project's PMs because it adds a feature, and we need to track it. |
Bump. CF UAA support makes a nice extended CFAR + CFCR story. |
@glestaris This seems like a good thing to prioritize |
prioritised |
the commit has been merged 67bfa22 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
This PR adds support to configure the
apiserver
to use OpenID Connect. This will allow using Google, Azure AD or even CF UAA for user authentication.