Info endpoint

[dpanayotov]

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:

{
    "token_issuer": "https://example.com"
}

Where example.com has .well-known/openid-configuration endpoint as per https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfigurationRequest

This 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

[n3wscott]

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?

[dpanayotov]

@n3wscott - I agree, 'url' should be present.
Can you provide more information about presenting the issuer name to the user? I assume token fetching will be hidden for the user