Many Organizations prefer to have SSO enabled for accessing the Wellnomics SaaS WRM site. In this guide we'll show you how to enable OAuth SSO via Azure. We'll be using the Authorization Code flow for this configuration.
Before you begin you'll need some information from Wellnomics, please contact Wellnomics support for the required URIs.
Step 1: In the Azure Portal go to App Registrations and select '+ New registration'
Step 2: Enter the name you'd like to use for this App
Step 2.1: Select who can access the API, most environments will use the Single Tenant option
Step 2.2: Select Web and enter the Redirect URI provided by Wellnomics (We'll be adding the second redirect URI later on)
Step 2.3: Click 'Register'
Step 3: Configure Authentication. In the App you just registered, select Authentication in the Manage section
Step 3.1: In Authentication, select Add URI and paste in the second redirect URI provided by Wellnomics
Step 4: Generate a Client Secret. Under Manage Select 'Certificates & secrets'
Step 4.1: Select '+ New client secret
Step 4.2: Enter a name for the secret, set your desired expiration date, and select 'Add' *When this expires you'll need to create a new secret and send it to Wellnomics Support to update your site, otherwise SSO will fail*
Step 4.3: Copy the Secret Value and save it for later when we send all the needed values to Wellnomics Support for configuration. *the value and ID in this example have been blacked out*
Step 5: Send the required info to Wellnomics Support. This includes;
- The Discover URI for OpenID
- Client Id
- Secret Value (Saved earlier, step when we created the secret)
- Authorization Endpoint
- Access token URI
In the images below we'll show you where to find all of these.
Client ID: In the Azure portal > App Registrations > the OAuth App you just created > Overview
For the remaining URIs: In the Application Overview select Endpoints
Refer the the image below for grabbing the remaining URIs
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article