Setting up authentication with Okta
Last updated
Was this helpful?
Last updated
Was this helpful?
Was this helpful?
The following guide will assist you in configuring your application to use Okta for authentication.
Log into the Okta admin console with administrative credentials, select Applications then Applications
Click Create app integration
Select Open ID Connect as the sign in method and Web application as the application type
Enter Lithnet Access Manager or another suitable application name and optionally provide a logo
Ensure that authorization code is the selected grant type
For the sign in redirect URI, enter the base URL where your Lithnet Access Manager app is hosted followed by /auth/ (e.g. https://accessmanager.lithnet.local/auth/)
Set the sign-out redirect URI to your base URL, and append /auth/logout to the end of it (e.g. https://accessmanager.lithnet.local/auth/logout)
Assign the appropriate users to the app and save the new app
From the new app page, copy the client ID and client secret value for use later in the setup process
Select Directory from the main menu bar, and select Profile editor. Find the Lithnet Access Manager app in the list, and click the app name to open the profile editor.
Click Add attribute and create a new attribute with a display name and variable name of upn, of data type string. Select attribute required and select personal as the attribute type. Save the new attribute
Click the Mappings button. Scroll down until you fine the upn attribute in the right hand app attributes column, and on the left side, select the Okta attribute that contains the Active Directory UPN (e.g. aduser.userPrincipalName). Change the arrow to Apply mapping on user create and update
Open the Lithnet Access Manager Service Configuration Tool
Select the App configuration\User Authentication page
Select Open ID Connect as the authentication provider
Enter the URL of your Okta tenant in the Issuer/Authority field
Enter the client ID and secret obtained from the Okta setup process
We strongly recommend modifying your application sign-on policy to require multifactor authentication for the use of this app.
AMS maps upn, sid and onprem_sid claims automatically if they are found in the response from the IDP.
If you need to use an attribute other than those, you can configure a custom claim mapping using PowerShell