Implementing single sign-on in Assets Server using Okta

Note: The images and steps in this article are those from the Classic UI. When logged in to Okta with a developer account, the Admin UI is shown which differs in places from the Classic UI. It is advised to switch to the Classic UI to correctly follow the steps.

Before you start

Before you start, make sure that:

The Assets Server environment in which Okta is implemented has a fully working Assets Server and fully working client applications.

Notes about setting up users and user groups in Assets Server:

Apart from an admin user, users do not have to be set up in Assets Server; when a user logs in, these will be automatically created.

User groups in Assets Server should have the same name as the user groups in Okta.

When using SAML and/or LDAP, disable it.

You have access to Okta and you have sufficient access rights to configure Okta

Okta is set up to your needs, for example by setting up additional security rules.