SAML
For teams using Okta as their enterprise identity provider, Okta recommends using the Okta Workforce integration, but you can also use the SAML integration to configure SSO.
Here are the steps you need to take to configure Okta as a SAML-based identity provider.
Step 1: Contact your Scanner support team to get Single Sign-On URL and Audience URI
When you create your Okta SAML application integration, you will need two pieces of information first:
Single sign-on URL. It will be a URL with this format:
https://login.scanner.dev/login/callback?connection=<connection-name>&organization=<org-id>
Audience URI (SP Entity ID). It will be an identifier with this format:
urn:auth0:scanner-production:<connection-name>
Contact your Scanner support team (either in your enterprise's private Slack channel or email) to start the process and receive these values.
Step 2: Create Okta SAML Application Integration
Within your Okta dashboard, navigate to Applications > Applications.
Click Create App Integration.
For the Sign-in method, select SAML 2.0. Click Next.
Set the App integration name to "Scanner.dev" or another name if you like. The logo is optional, but here is a link to a logo image you can download and use. Click Next.
For Single sign-on URL, enter the value given earlier by your Scanner support team. It will be a URL with this format:
https://login.scanner.dev/login/callback?connection=<connection-name>&organization=<org-id>For Audience URI (SP Entity ID), enter the value given earlier by your Scanner support team. It will be an identifier with this format:
urn:auth0:scanner-production:<connection-name>Click Next.
Under Did you find SAML docs for this app?, add the URL to the Scanner documentation, eg. https://docs.scanner.dev.
Click Finish.
Step 3: Assign a group to the application
If you don't already have a Group in Okta containing users that will access Scanner, you can create a new group.
Navigate to Directory > Groups.
Click Add group.
Set the name to "Scanner Users".
In the group details, navigate to Applications, and click Assign applications.
Search for "Scanner.dev", or whatever the name was that you gave to the application.
Add users to the group.
Step 4: Send URLs and Signing Certificate to Scanner
You should now see the details of the new application integration.
Under Sign On > Settings > Sign on methods > SAML 2.0, click More details.
You should see the Sign on URL and Sign out URL. Copy-paste these somewhere.
Click to download the Signing Certificate.
Contact your Scanner support team (either in your enterprise's private Slack channel or email), who will help you in the process of sending the Sign on URL, Sign out URL, and Signing Certificate.
Step 5: Scanner support engineer will complete the integration
Your Scanner support engineer will create the new SSO integration and connect it to your Scanner instance.
The engineer will configure the integration such that all users with your enterprise's email domain will be directed to your Okta SSO login system. Coordinate with the engineer to decide what email domain(s) to use here.
Step 6: Log in to Scanner
Visit the Scanner app to log in.
Enter your email address (should use your enterprise's email domain).
Scanner will redirect to Okta, where you can log in.
You'll be redirected to Scanner and can now use the application.
Note: At this point, you will have access to Scanner, but one of your team members with user invitation permissions must also add you to a team and give you an appropriate user role in Scanner before you can view data.
Last updated