The Okta/Idiomatic SAML integration currently supports the following features:
For more information on the listed features, visit the Okta Glossary.
Contact the Idiomatic Support team (support@idiomatic.io) and request that they enable SAML 2.0 for your account. Also ask them to provide you with your Organization ID value.
Save the following metadata as idp_metadata.xml and attach it to your request:
Sign in to Okta Admin app to have this variable generated for you.
The Idiomatic Support team will process your request and provide you with your Organization ID value.
In Okta, select the Sign On tab for the Idiomatic app, then click Edit.
Scroll down to the ADVANCED SIGN-ON SETTINGS section.
Enter the Organization ID value from step 3 into the corresponding field.
Click Save:
Make sure that you selected the correct value in the Environment field under the General application tab in Okta. Using wrong values will prevent you from authenticating via SAML to Idiomatic.
Since the only SP-initiated flow is supported we recommend to hide application icon for users and add a Bookmark app. Follow the instructions below in order to hide the Idiomatic application and add a Bookmark application:
Simulating an IDP-initiated Flow with the Bookmark App
Use the following bookmark application configuration settings:
Application label: Idiomatic
URL:
Production environment: https://idiomatic.io/saml/login?client_name=samlOrg[organizationId]
Staging environment: https://staging.idiomatic.io/saml/login?client_name=samlOrg[organizationId]
Where [organizationId] is your Organization ID value received in step 3.
The following SAML attributes are supported:
Name | Value |
---|---|
first_name | user.firstName |
last_name | user.lastName |
user.userName |
Open your Idiomatic login URL:
Production environment: https://idiomatic.io/
Staging environment: https://staging.idiomatic.io/
Click the Log in link.
Select Sign in using Okta:
Enter your email address, then click SIGN IN:
Open the following URL:
Where [organizationId] is your Organization ID value received in step 3.