📄️ SSO Authentication Options
This topic discusses how to set up SSO authentication for external users that are in external IDPs.
📄️ Set up the OpenID Connect (OIDC) Authentication for Release
This topic describes how to configure Release authentication using the OpenID Connect (OIDC) protocol. OpenID Connect (OIDC) is an identity layer built on top of the OAuth 2.0 protocol and supported by various OAuth 2.0 providers.
📄️ Configure OpenID Connect (OIDC) Authentication With Keycloak
This topic describes how to configure Keycloak to authenticate Release users and REST API calls (using the Bearer Token Authorization).
📄️ Set up LDAP Authentication
This topic describes how to configure Release to use an LDAP repository to authenticate users and retrieve role, group, membership.
📄️ Integrated Windows Authentication
This topic describes how support Single Sign-On (SSO) by configuring Release to use Integrated Windows Authentication to authenticate users and retrieve role (group) membership without prompting the users for a user name and password. In Release, Active Directory users and groups become principals that you can assign to roles.
📄️ Personal Access Token for Authentication
This topic describes how to create and use Personal Access Tokens (PAT).
📄️ Integrate Release with Digital.ai Platform Identity Service
This guide provides step-by-step instructions for integrating Digital.ai Release with the Digital.ai Platform.
📄️ Configure Maximum Size of the HTTP Request Header
With the maximum size of the HTTP request header set to 8KB (8192 bytes) it becomes difficult to pass the authentication tokens and scopes in headers. Hence with Release 24.1 and later, you can use the server.max-http-request-header-size parameter to configure the maximum size of the HTTP request header that the Release server can accept. Setting an appropriate value for this parameter depends on the specifics of your application and environment.