Skip to main content
All CollectionsPlatformSingle Sign-On (SSO)
SSO - Okta Configuration Example
SSO - Okta Configuration Example

This example shows you how to configure Okta for Frontify.

Updated over 3 months ago

SSO (Single Sign-On) offers a quick and convenient login method for all employees. With SSO, you can automatically grant viewing access to all, or selected, employees within your company. SSO is available as an add-on for Enterprise accounts. For more details, please refer to our introduction and FAQ.


To begin the SSO setup process, contact your Customer Success Manager.
Once in the setup process, you can use the example below if you use Okta.


Group attributes with Okta

User groups help manage access permissions to Style Guides, Projects, Libraries. By assigning the right people to the right group you can avoid individually inviting everyone to specific content.

With SSO group mapping, you can set up groups based on your internal departments, functions, or other commonalities and assign several team members to various projects at once. Learn more about setting up User Groups with SSO (group mapping).

Based on our experience, we have found a working way that shows you how to send your group's details from Okta to Frontify:

  1. Create the attribute User.Groups in your SAML settings that matches regex values:

The plain text of the regex filter might look like one of these scenarios:

.*Marketing.*|.*Sport.*|.*Brand.*

OR

\.*Marketing\.*|\.*Sport\.*|\.*Brand\.*

The values are matching the group names in your Okta account:

2. Then add sso_mapping values in the Frontify User Management page -> Groups tab. This is described in detail in the User Groups with SSO (group mapping) article.

3. Test if the setup works. Ask a user from your user directory that belongs to a group on your end to logging in to Frontify via SSO.

On the User Management page, check if the user belongs to the mapped group. You can also invite the mapped group to a Style Guide and see if the user has group-based permission to the Style Guide.


โ€‹

Did this answer your question?