Skip to main content
Version: v2.15.x LTS

Zowe User Authentication

Last updated
:  |
... min read
|
Edit this page
Print
Open doc issue

Zowe User Authentication

The API Mediation Layer provides multiple methods which clients can use to authenticate.

Authentication with JSON Web Tokens(JWT)​

When the user successfully authenticates with the API ML, the client receives a JWT token in exchange. This token can be used by the client to access REST services behind the API ML Gateway and also for subsequent user authentication. The access JWT Token is signed with the private key that is configured in the Zowe Identity Provider's certificate store, regardless of whether the token is in a keystore or keyring.

To utilize Single-Sign-On (SSO), the Zowe API ML client needs to provide an access token to API services in the form of the cookie apimlAuthenticationToken, or in the Authorization: Bearer HTTP header as described in this authenticated request example.

Authentication with client certificates​

If the keyring or a truststore contains at least one valid certificate authority (CA) other than the CA of the API ML, it is possible to use client certificates issued by this CA to authenticate to the API ML.

For more information, see the Authentication for API ML services documentation

Authentication with Personal Access Token (PAT)​

A Personal Access Token (PAT) is a specific scoped JWT with a configurable validity duration. The PAT authentication method is an alternative to using a client certificate for authentication. It is disabled by default. To enable this functionality, see Enabling single sign on for clients via personal access token configuration.

Benefits of PAT

  • Long-lived. The maximum validity is 90 days.
  • Scoped. Users are required to provide a scope. It is only valid for the specified services.
  • Secure. If a security breech is suspected, the security administrator can invalidate all the tokens based on criteria as established by rules.

For more information about PAT, see Authenticating with a Personal Access Token documentation.

Authentication with SAF Identity Tokens​

The SAF Authentication Provider allows the API Gateway to authenticate the user directly with the z/OS SAF provider that is installed on the system.

For more information about configuring the token, see Configure signed SAF Identity tokens (IDT).

Multi-factor authentication (MFA)​

Multi-factor authentication is provided by third-party products which Zowe is compatible with. The following are known to work with Zowe:

Additionally, Zowe API ML can be configured to accept OIDC/OAuth2 user authentication tokens. In this particular case, MFA support is built into the OIDC provider system. It does not rely on the mainframe MFA technology, but is equally secure.

For details about multi-factor authentication, see the MFA documentation here.

Certificate Authority Advanced Authentication Mainframe (CA AAM)​

To add a dynamic element to the authentication, you can configure the Certificate Authority Advanced Authentication Mainframe to enable multi-factor authentication. For more information about CA AAM, see the Advanced Authentication Mainframe documentation.

On this page