Lithnet Access Manager
PricingRequest a trial or quoteDownloads
v1.0
v1.0
  • Home
  • How does Access Manager help prevent lateral movement
  • Access Manager Editions
  • Licensing
  • Change log
  • Installation
    • Downloads
    • Creating a service account for the Access Manager service
    • Choosing between the Microsoft and Lithnet agents for LAPS support
    • Installing Access Manager
      • Access Manager Agent
      • Access Manager Service
  • Configuration
    • Setting up Authentication
      • Setting up smart card authentication
      • Setting up authentication with ADFS
      • Setting up authentication with Azure AD
      • Setting up authentication with Okta
    • Deploying features
      • Setting up Microsoft LAPS
      • Setting up Bitlocker access
      • Setting up Just-in-Time access
      • Setting up password encryption and history
      • Installing in a Failover Cluster
      • Integrated Windows authentication
    • Importing authorization rules
      • Importing BitLocker permissions
      • Importing local administrators group membership
      • Importing Microsoft LAPS permissions
      • Importing mappings from a CSV file
      • Importing rules from Lithnet LAPS web app
  • Help & Support
    • Frequently asked Questions
    • Troubleshooting
    • Getting Support
  • Advanced help
    • Advanced help topics
      • Access evaluation in Access Manager Service (AMS)
      • Performing an offline discovery of local admins
      • Script-based authorization
      • Backing up Access Manager
      • Recovering from a lost encryption certificate private key
    • Application help pages
      • Active Directory
      • Audit variables
      • Auditing Page
      • Auditing scripts
      • Authentication Provider
      • Authorization Page
      • BitLocker Page
      • Effective Access Page
      • SMTP Server Settings
      • High Availability Page
      • Proxy Settings
      • Jit Access Page
      • Licensing-Page
      • Local Admin Passwords Page
      • Rate Limits Page
      • User Interface Page
      • Web Hosting Page
Powered by GitBook
On this page
  • Configure a new application in Okta
  • Configure Lithnet Access Manager
  • Enable multi-factor authentication

Was this helpful?

  1. Configuration
  2. Setting up Authentication

Setting up authentication with Okta

The following guide will assist you in configuring your application to use Okta for authentication.

Configure a new application in Okta

  1. Log into the Okta admin console with administrative credentials, select Applications then Applications

  2. Click Add application, then Create app integration

  3. Select Open ID Connect as the sign in method and and Web application as the application type

  4. Enter Lithnet Access Manager or another suitable application name and optionally provide a logo

  5. Ensure that authorization code is the selected grant type

  6. For the sign in redirect URI, enter the base URL where your Lithnet Access Manager app is hosted followed by /auth/ (eg https://accessmanager.lithnet.local/auth/)

  7. Set the sign out redirect URI to your base URL, and append /auth/logout to the end of it (eg https://accessmanager.lithnet.local/auth/logout)

  8. Assign the appropriate users to the app and save the new app

  9. From the new app page, copy the client ID and client secret value for use later in the setup process

  10. Select Directory from the main menu bar, and select Profile editor. Find the Lithnet Access Manager app in the list, and click the Profile button

  11. Click Add attribute and create a new attribute called upn, of data type string. Select both the attribute required and User personal check boxes

  12. Click the Mappings button. Find the UPN value, and map it to the okta attribute that contains the Active Directory UPN (eg aduser.userPrincipalName)

Configure Lithnet Access Manager

  1. Open the Lithnet Access Manager Service configuration tool

  2. Go to the Authentication page and select OpenID Connect as the authentication provider

  3. Enter the URL of your okta tenant in the Issuer/Authority field

  4. Enter the client ID and secret obtained from the Okta setup process

Enable multi-factor authentication

We strongly recommend to modify your application sign-on policy to require multi-factor authentication for the use of this app.

PreviousSetting up authentication with Azure ADNextDeploying features

Last updated 2 years ago

Was this helpful?