Authentication and Keys
You can use the Authentication and Keys page to allow on-premise customers to use credentials issued by an IdP that supports SAML 2.0 to log into
Clarity. You can also use key-based authentication to generate a personal API key for a specific client based on a user's SSO credentials, access rights, and status settings.
Clarityto Support SAML 2.0
Clarityallows on-premise customers to use the credentials issued by an IdP - that supports SAML 2.0 - and log into
Some key advantages of using SAML-based SSO login are:
- Seamless integration between networks and environments: All users can move easily between your organization's intranet andClarity.
- Simplified password management: No need to manage user passwords separately fromClarity, because your existing user management system handles password management.
- Simplified Certificate management: UseClarityto manage various security certificates.
To learn more about SAML authentication, see Configuring Clarity to Support SAML 2.0.
Key-based authentication uses a personal API key that is generated for a specific client based on a user's SSO credentials, access rights, and status settings. Key authentication eliminates the need to generate and pass credentials or tokens for every session. Use key authentication in the following scenarios:
- You want to integrate data betweenClarityand other client applications. Integration architectures can allow users to authenticate through the REST API and accomplish certainClarityactions without going into the user interface.
- YourClarityinstance is using SSO for authentication.
Rallyintegration could make webhook calls to read
Clarityproject data personalized for the current user. For project managers, third-party integration could read and update resource allocation data in
Claritybased on external application triggers such as other users updating a JIRA Kanban board.
To learn more about key-based authentication, see REST API Authentication.