Hide Forgot
Document URL: https://docs.openshift.com/dedicated/3.2/dev_guide/authentication.html Section Number and Name: CLI Authentication Describe the issue: Authentication with Dedicated (cli) requires the use of a "token" Suggestions for improvement: Only document how to authenticate with a token, and document how `oc login` shows users where to get this token. Additional information: > $ ./oc login https://api.COOLCORP.openshift.com > Login failed (401 Unauthorized) > You must obtain an API token by visiting https://api.COOLCORP.openshift.com/oauth/token/request
(In reply to Eric Rich from comment #0) > Document URL: > https://docs.openshift.com/dedicated/3.2/dev_guide/authentication.html > > Section Number and Name: CLI Authentication > Describe the issue: Authentication with Dedicated (cli) requires the use of > a "token" > > Suggestions for improvement: Only document how to authenticate with a token, > and document how `oc login` shows users where to get this token. > > Additional information: > > > $ ./oc login https://api.COOLCORP.openshift.com > > Login failed (401 Unauthorized) > > You must obtain an API token by visiting https://api.COOLCORP.openshift.com/oauth/token/request This should only be applied to OpenID or OAuth providers, or providers that do not support challange/login options from: https://docs.openshift.com/enterprise/3.2/install_config/configuring_authentication.html#identity-providers
Some dedicated installations support username/password logins. `oc login` should continue to be the main starting point for the CLI login procedure. There is nothing more specific we can document that would apply to all installations, since the web flow required to obtain a token is located at a different URL for all dedicated installations. I would recommend we leave the docs as-is