okta saml.md

For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending .md to page URLs; this page is available as Markdown.

Signing in with Okta

This document details configuring Okta SAML for authentication with Dropzone. This is more advanced than using federated buttons such as "Log in with Google" and "Log in with Microsoft" but offers more customization, especially useful for customers with more than one Dropzone environment.

Enabling SAML with Okta involves the following steps:

Create the Dropzone Role on User Profile

Dropzone needs to know which role a user should receive when logging into your tenant. There are multiple ways you can configure this, but the most common is to add a field to the user profile or to the Okta application profile.

Here we show you how to add the field to the user Okta profile.

Display Name Value
admin admin
member member
restricted-read-only restricted-read-only

Assign Dropzone Role Attributes to Users

Next, set the dropzone_role profile value for users who will have access to the Dropzone AI platform.

Create the Okta Application

Name Value
first_name user.firstName
last_name user.lastName
full_name user.fullName
dropzone_role user.dropzone_role

Assign Users to the Dropzone Application

Configure which users are allowed to log into Dropzone.

Gather Application Data for Dropzone

Dropzone needs two pieces of information from your Okta environment to enable the SAML trust.

Find the following two pieces of information:

Provide these to your Dropzone support representative. (Typically this is done via the Dropzone SAML Request form.)

Update Your SAML Application

Dropzone will enable SAML and provide you two values to add to the "SAML Settings" in the "General" tab of your SAML app:

Update these values in your Okta Application and save.

Set Legacy Configuration on your app

In addition to setting the roles as custom profile attributes, on the app itself: Navigate to Sign On > Show Legacy Configuration > Profile attribute statements Set dropzone_role equal to appuser.dropzone_role

Advanced Okta

Okta has powerful configuration capabilities, including Okta Expression Language which can be used to simplify your Dropzone role provisioning, as an alternative to manually setting roles on a user's profile directly.

Advanced Okta - Drozone Role via Group Membership

Some customers use Okta Groups coupled with Okta Expression language to populate the dropzone_role attribute automatically. As an example, say you had the following groups:

You could use the following

user.isMemberOfGroupName("access-dropzone-admin") ? "admin" :
user.isMemberOfGroupName("access-dropzone-member") ? "member" :
user.isMemberOfGroupName("access-dropzone-read-only") ? "restricted-read-only" :
null

The values (e.g. admin, member, restricted-read-only on the right side above) must match exactly the values we expect, however the groups can be anything that matches your internal naming standards.

Getting Help

If you have any errors or questions, engage your Dropzone AI support representative.