7 docs tagged with "authentication"

Release has a role-based security system with two types of users:

This topic describes how to configure Keycloak to authenticate Release users and REST API calls (using the Bearer Token Authorization).

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.

Keycloak is the the default authentication manager for Release. This topic describes the steps involved in configuring Keycloak before and after the Release installation.

Digital.ai Release has a role-based security system with two types of users:

Personal Access Tokens (PAT) are used as an alternative to passwords for authenticating with Digital.ai Release. You can use PATs with public APIs and webhook endpoints.

* 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.