Files.com supports Okta SSO via OAuth or OpenID Connect (OIDC). SCIM provisioning is only compatible with SAML-based integration, not OAuth or OpenID Connect. For SAML setup, see the Okta SSO page.

Adding Files.com in Okta

After logging in to your Okta account as an administrator, navigate to Applications and click the Create App Integration button.

Select OIDC - OpenID Connect as sign-in method, and select Web Application as the Application type, and then click the Next button.

In the form, enter Files.com in the App Integration Name field, and enter the following URL in the Sign-in redirect URIs field. You can use the same URL for Sign-out redirect URIs.

https://app.files.com/login_from_oauth?provider=okta

Select the appropriate option under Controlled access in the Assignments section based on your requirements.

Click the Save button to finish adding the application. In the integration summary page, find the Client Credentials box. Click the clipboard icon next to the Client ID to copy it. Keep this browser tab open, as you'll be returning here to copy the Client Secret later.

Adding Okta in Files.com

A site administrator can add a new SSO Provider to your site. Select Okta as the provider type and select Use OAuth.

Provide a Display Name for your new provider. This is shown on the login page of your Files.com site.

Enter your Okta subdomain into the Subdomain field, and paste the Client ID you copied in the previous step into the Client ID field.

Copy your Client secret from Okta, and paste it into the Client secret field in Files.com.

The Okta SSO method will now be available when assigning an authentication method for a user in Files.com, and the Sign in with Okta button will be displayed on your site's login page.

Keep at least one site administrator on password authentication rather than assigning every administrator to SSO. This prevents lockout if your IdP or SSO configuration has issues.