SSO with Okta
Integrate Okta as the identity provider for Awell, using a SAML app integration.
With Okta as the identity provider (IdP), people sign in to Awell with their Okta credentials. The connection is a Security Assertion Markup Language (SAML) app integration in Okta.
Before starting
- An active Okta account with administrative access.
- An Awell account with permission to configure single sign-on (SSO). Awell provides an ACS URL, an Audience URI and a Connection ID on request.
Request SSO from Awell first; step 2 can't be completed without those three values.
1. Create and configure a new Okta application
Follow Okta's guide for adding a SAML application.
2. Create the SAML app integration
Complete the SAML integration using the ACS URL, Audience URI and Connection ID from Awell.
3. Gather the SAML configuration details from Okta
Collect the details Okta generates, including its metadata.
4. Assign users in Okta
Assign the application to the users and groups who should have Awell access.
As with any IdP, assigning the application is the ongoing access process: with just-in-time provisioning an assigned user's Awell profile is created the first time they log in.
5. Provide the Okta details to Awell
Send the details to Awell, who complete the connection.
Awell completes the connection
Awell finishes the configuration and confirms when SSO is live. Test with one user before assigning everyone.
Next steps
Once people can sign in, assign them the right roles.
SSO with Google
Integrate Google Workspace as the identity provider for Awell, using a custom SAML app.
Platform, security and compliance FAQ
Direct answers to the questions prospects, security reviewers and procurement teams ask most about Awell's architecture, security posture, data handling and regulatory position.