-
Notifications
You must be signed in to change notification settings - Fork 4
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
Info endpoint #26
Comments
I would suggest that "uri" or "url" be present in the field to make it clear this is not a key, but rather a URI. Also a name for the issuer to present to the user when the CLI is doing token fetching? |
@n3wscott - I agree, 'url' should be present. |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Service Manager could expose an unsecured endpoint that provides information that can be used when accessing its APIs.
This endpoint would be of use to the CLI. It can obtain the endpoints for issuing and refreshing tokens when calling the Service Manager's APIs.
Example:
GET /v1/info
Reponse:
Where example.com has
.well-known/openid-configuration
endpoint as per https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfigurationRequestThis configuration used in the Service Manager authentication should be similar to https://kubernetes.io/docs/admin/authentication/#openid-connect-tokens whereas this info endpoint could be similar to https://apidocs.cloudfoundry.org/268/info/get_info.html
The text was updated successfully, but these errors were encountered: