Introduction to Single Sign-On

You can integrate Resolve Actions with third-party SAML Identity Providers (IdPs) such as Azure, Ping Identity, or Okta, as well as with any custom SAML service. This way, your users will be able to reuse their existing Single Sign-On (SSO) accounts on Actions. Actions only supports Azure Active Directory (AD) as a directory service; your IdP must also synchronize with the same Azure AD as Actions.

Actions supports Service Provider-initiated SSO. The protocol version that Actions supports is SAML 2.0.

You can only integrate with a single SSO provider at any given time.

You can use SSO and the local Actions authentication mechanism in parallel. For example, your administrators could be using local accounts while your automation developers are on SSO accounts. You cannot log in to the same account using both local and SSO authentication, but you can provide different accounts with access to the same content using roles and permissions.