Authentication | Developer Guide

Web Console Authentication
cli Authentication

Web Console Authentication

When accessing the web console from a browser at <master_public_addr>:8443, you are automatically redirected to a login page.

Figure 1. Web Console Login Page

Review the browser versions and operating systems that can be used to access the web console.

You can provide your login credentials on this page to obtain a token to make API calls. After logging in, you can navigate your projects using the web console.

cli Authentication

You can authenticate from the command line using the cli command oc login. You can get started with the cli by running this command without any options:

$ oc login

The command’s interactive flow helps you establish a session to an OKD server with the provided credentials. If any information required to successfully log in to an OKD server is not provided, the command prompts for user input as required. The configuration is automatically saved and is then used for every subsequent command.

All configuration options for the oc login command, listed in the oc login --help command output, are optional. The following example shows usage with some common options:

$ oc login [-u=<username>] \
  [-p=<password>] \
  [-s=<server>] \
  [-n=<project>] \
  [--certificate-authority=</path/to/file.crt>|--insecure-skip-tls-verify]

The following table describes these common options:

Table 1. Common **cli** Configuration Options
Option	Syntax	Description
`-s, --server`	$ oc login -s=<server>	Specifies the host name of the OKD server. If a server is provided through this flag, the command does not ask for it interactively. This flag can also be used if you already have a cli configuration file and want to log in and switch to another server.
`-u, --username` and `-p, --password`	$ oc login -u=<username> -p=<password>	Allows you to specify the credentials to log in to the OKD server. If user name or password are provided through these flags, the command does not ask for it interactively. These flags can also be used if you already have a configuration file with a session token established and want to log in and switch to another user name.
`-n, --namespace`	$ oc login -u=<username> -p=<password> -n=<project>	A global cli option which, when used with `oc login`, allows you to specify the project to switch to when logging in as a given user.
`--certificate-authority`	$ oc login --certificate-authority=<path/to/file.crt>	Correctly and securely authenticates with an OKD server that uses HTTPS. The path to a certificate authority file must be provided.
`--insecure-skip-tls-verify`	$ oc login --insecure-skip-tls-verify	Allows interaction with an HTTPS server bypassing the server certificate checks; however, note that it is not secure. If you try to `oc login` to a HTTPS server that does not provide a valid certificate, and this or the `--certificate-authority` flags were not provided, `oc login` will prompt for user input to confirm (`y/N` kind of input) about connecting insecurely.

cli configuration files allow you to easily manage multiple cli profiles.

If you have access to administrator credentials but are no longer logged in as the default system user system:admin, you can log back in as this user at any time as long as the credentials are still present in your cli configuration file. The following command logs in and switches to the default project:

$ oc login -u system:admin -n default