Securing IBM z/OS Connect resources for zosConnect-3.0

z/OS Connect resources can be secured through a range of standard mechanisms.

zosConnect-3.0 Applies to zosConnect-3.0.

Overview of IBM z/OS Connect zosConnect-3.0 security
IBM® z/OS Connect security can operate with Lightweight Directory Access Protocol (LDAP), open standards such as Transport Layer Security (TLS), and with third-party authentication JSON Web Tokens (JWT) and, when running on z/OS, traditional z/OS security such as System Authorization Facility (SAF).
API provider confidentiality and integrity for zosConnect-3.0
Learn how to maintain the confidentiality and integrity of the data that is handled by IBM z/OS Connect for OpenAPI3 APIs.
API provider authentication and identification
Learn how requests sent to IBM z/OS Connect are authenticated.
API provider authorization
Learn how IBM z/OS Connect authorizes access to APIs.
API provider audit
Learn how IBM z/OS Connect audits access to z/OS Connect APIs.
API provider security for z/OS Assets
Learn about the security options available for connections between IBM z/OS Connect and Systems of Record (SoRs).
API requester confidentiality and integrity for zosConnect-3.0
Learn how to maintain the confidentiality and integrity of the data that the IBM z/OS Connect zosConnect-3.0 feature handles for API requesters that call OpenAPI 2.0 or OpenAPI 3.0 REST APIs.
API requester authentication and identification
Learn how requests in API requester scenarios are authenticated and identified.
API requester authorization
Learn how IBM z/OS Connect authorizes access to invoke API requesters.
User registries
To use authentication or authorization with IBM z/OS Connect, you require a user registry.
Configuring the Liberty Angel process and z/OS authorized services
You must configure the Liberty Angel process so that IBM z/OS Connect can use z/OS authorized services.
Configuring named angels
Configuring multiple angel processes in an LPAR.

Parent topic: Securing with IBM z/OS Connect