This CR SessionHandling specifies the Redis database where sessions should be stored. Session sharing between different Microgateway deployments, i.e., for single sign-on (SSO), can be configured by setting the prefix and persistence back-end to be the same across all corresponding SessionHandling CRs.
Session cookies are currently never shared across different (sub-)domains. Authentication via different OIDC Relying Parties generates different session cookies. Clients will, therefore, only be able to transparently reuse session cookies for connecting to different Airlock Microgateway deployments if those are:
- exposed under the same domain
- handle authentication via the same OIDC Relying Party.
and
Configuration details can be found in the CR SessionHandling reference documentation. See also the article CR RedisProvider for Redis configuration details.
This CR needs to be referenced in the CR SidecarGateway.