CR AccessControl

Airlock Microgateway can be configured to perform authorization, authentication and identity propagation using the CR AccessControl. For session handling, access control requires a Microgateway Session Agent setup with a Redis database. See also article Microgateway Session Agent.

• List of referenceable CRs:
• CR IdentityPropagation
• CR OIDCRelyingParty

This CR needs to be referenced in the CR SidecarGateway.

• Licensed module for Community vs. Premium editions in detail.
• Airlock IAM or another OIDC provider for OIDC authentication.
• A Redis database configured for session handling.

For the default and an example configuration, see CR AccessControl reference documentation.

• About the example configuration:
• The CR OIDCRelyingParty specifies how the Airlock Microgateway Engine interacts with an OpenID Provider (OP) to authenticate the user.
• The CR IdentityPropagation specifies how the identity of the authenticated user is propagated from the Microgateway Engine to the back-end.

• API Reference:
• CR SidecarGateway reference documentation
• CR OIDCRelyingParty reference documentation
• CR IdentityPropagation reference documentation

• Internal links:
• Referenced by CR SidecarGateway
• References CR OIDCRelyingParty
• References CR IdentityPropagation
• Requires Microgateway Session Agent