This topic describes how to configure Release to use an Atlassian Crowd to authenticate users and retrieve role (group) membership. In Release, Atlassian Crowd users and groups become principals that you can assign to roles. Global permissions are assigned at the role level.
This topic describes how to configure Keycloak to authenticate Release users and REST API calls (using the Bearer Token Authorization).
This topic outlines how to configure session timeout and session storage settings in Release.
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.
This topic describes how to configure Release to use an LDAP repository to authenticate users and retrieve role, group, membership.
This topic explains the role-based access control (RBAC) system in Digital.ai Release, which includes managing both internal users created and managed within Release and external users maintained in external identity providers.
This topic describes how to create and use Personal Access Tokens (PAT).
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.
This topic explains user management in Digital.ai Release, including how users are identified and authenticated through valid credentials.