You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2021. It is now read-only.
Currently /api/token?for=<cluster_url> requires loading the cluster URL from user's profile via /api/user to construct a proper request (for example /api/token?for=https://api.starter-us-east-2.openshift.com).
We can add a special alias for the user's cluster URL, something like /api/token?for=openshift. Auth service will look up for the cluster URL where the user is provisioned to and will return the token for that cluster. Plus we can add provider_api_url claim to the result:
* Add alias for user's OSO/github url to GET /api/token?for=<alias>
* Add alias for user's OSO/github url to POST /api/token/link?for=<alias>
* Add alias for user's OSO/github url to DELETE /api/token?for=<alias>
fixes#334
Currently
/api/token?for=<cluster_url>
requires loading the cluster URL from user's profile via/api/user
to construct a proper request (for example/api/token?for=https://api.starter-us-east-2.openshift.com
).We can add a special alias for the user's cluster URL, something like
/api/token?for=openshift
. Auth service will look up for the cluster URL where the user is provisioned to and will return the token for that cluster. Plus we can addprovider_api_url
claim to the result:We also could return the same payload but without the token for
/api/token/status
:The text was updated successfully, but these errors were encountered: