Lithnet Access Manager
PricingRequest a trial or quoteDownloads
v3.0
v3.0
  • Home
  • How does Lithnet Access Manager help prevent lateral movement?
  • Access Manager Editions
  • Licensing
  • What's new in Access Manager v3
  • Change log
  • Installation
    • Getting started
    • System Requirements
    • Downloads
    • Upgrading from Access Manager v1
    • Upgrading from Access Manager v2
      • Considerations for migrating from Access Manager v2
    • Installing the Access Manager Server
      • Creating a service account for the Access Manager Service
      • SQL installation options
      • Installing the Access Manager Service
      • High availability options
        • Load balancing Access Manager
    • Installing the Access Manager Agent
      • Enabling agent support on the AMS server
      • Installing the Access Manager Agent on Windows
      • Installing the Access Manager Agent on Linux
      • Installing the Access Manager Agent on macOS
  • Configuration
    • Setting up Authentication
      • Setting up authentication with ADFS
      • Setting up authentication with Microsoft Entra ID
      • Setting up authentication with Okta
      • Setting up smart card authentication
      • Setting up integrated windows authentication
    • Deploying Features
      • Setting up RapidLAPS
      • LAPS
        • Setting up Microsoft LAPS for Active Directory
        • Setting up Microsoft LAPS for Entra
        • Setting up Lithnet LAPS
      • Just-in-time Authentication (JIT)
        • Setting up JIT for computers
        • Setting up JIT for roles
      • Setting up BitLocker access
        • Setting up access to BitLocker keys stored in Active Directory
        • Setting up BitLocker recovery key backup and access using the Access Manager Agent
    • Importing authorization rules
      • Import Microsoft LAPS permissions from Active Directory
      • Importing BitLocker permissions from Active Directory
      • Importing local administrator group membership from domain-joined Windows devices
      • Import mappings from a CSV file
      • Performing an offline discovery of local admins
  • Help and support
    • Frequently asked Questions
    • Troubleshooting
    • Quick start guides
      • Getting started with Windows LAPS and Lithnet Access Manager
      • Getting started with Windows LAPS for Active Directory
      • Getting started with Windows LAPS for Microsoft Entra
      • Getting started with RapidLAPS
    • Product lifecycle
    • Choosing between the Lithnet and Microsoft agent for LAPS
    • Support Articles
      • KB000001: The Access Manager Agent cannot connect and logs a token-validation-failed error
      • KB000002: Users retain their admin rights after their JIT period expires
      • KB000003: Configuring the Access Manager Agent to manage an account other than 'root' on Linux
      • KB000004: Creating a log file to troubleshoot installation issues with the Access Manager Service
      • KB000005: Access Manager stops working after applying the November 2022 Windows update
      • KB000006: Migrating the Access Manager Database
      • KB000007: Adding JIT groups via Group Policy doesn't work with NTLM Disabled
      • KB000008: AMS is unable to JIT into privileged groups such as Domain Admins
      • KB000009: Access Manager may return an out-of-date LAPS password, or no password at all
      • KB000010: The Access Manager agents fail to register on macOS 15 (Sequoia)
      • KB000011: Users report delays in obtaining just-in-time access via AD
      • KB000012: Troubleshooting Windows authentication in the Access Manager Web App
      • KB000013: Access Manager cannot be installed on Windows Server 2016 with TLS 1.0 disabled
    • Advanced help topics
      • Creating an Entra app registration or Access Manager
      • Setting up agent policies
      • Managing word lists
      • Password history retention
      • Ports and traffic flows
      • Internet access requirements
      • Access evaluation in Access Manager Service (AMS)
      • Recovering from a lost encryption certificate
      • Script-based authorization
      • Customized auditing with PowerShell notification channels
      • Variables available in audit notification channels
      • Setting up audit templates
      • Backup and Restore
      • Event ID reference
      • Group policy configuration
    • PowerShell reference
      • Add-AmsDeviceRegistrationKeyGroup
      • Add-AmsGroupMember
      • Add-AmsIdpClaimMapping
      • Clear-AmsIdpClaimMapping
      • Export-AmsServerDiagnostics
      • Get-AmsActiveDirectoryJitOptions
      • Get-AmsActiveDirectoryJitGroupCreationRule
      • Get-AmsComputerAuthorizationRule
      • Get-AmsDevice
      • Get-AmsDeviceRegistrationKey
      • Get-AmsFveRecoveryKey
      • Get-AmsGroup
      • Get-AmsGroupMembers
      • Get-AmsHostConfig
      • Get-AmsIdpClaimMapping
      • Get-AmsJitSchedulerJob
      • Get-AmsLocalAdminPassword
      • Get-AmsLocalAdminPasswordHistory
      • Get-AmsRoleAuthorizationRule
      • Get-AmsServiceConfig
      • New-AmsActiveDirectoryJitGroupCreationRule
      • New-AmsComputerAuthorizationRule
      • New-AmsDeviceRegistrationKey
      • New-AmsGroup
      • New-AmsRoleAuthorizationRule
      • Remove-AmsActiveDirectoryJitGroupCreationRule
      • Remove-AmsComputerAuthorizationRule
      • Remove-AmsDevice
      • Remove-AmsDeviceRegistrationKey
      • Remove-AmsDeviceRegistrationKeyGroup
      • Remove-AmsGroup
      • Remove-AmsGroupMember
      • Remove-AmsJitSchedulerJob
      • Remove-AmsRoleAuthorizationRule
      • Set-AmsActiveDirectoryJitGroupCreationRule
      • Set-AmsActiveDirectoryJitOptions
      • Set-AmsComputerAuthorizationRule
      • Set-AmsDevice
      • Set-AmsDeviceRegistrationKey
      • Set-AmsGroup
      • Set-AmsHostConfig
      • Set-AmsRoleAuthorizationRule
      • Set-AmsServiceConfig
    • Application help pages
      • Host configuration page
      • App Configuration
        • AMS License configuration page
        • Authentication configuration page
        • Email configuration page
        • Rate limit configuration page
        • IP Address detection configuration page
        • User interface configuration page
        • Auditing page
        • Security page
        • Database configuration page
      • Access Manager Agent
        • Access Manager Agent - Agent registration page
        • Agent Policies
          • Access Manager Agent - Windows polices page
          • Access Manager Agent - macOS polices page
          • Access Manager Agent - Linux polices page
          • Access Manager Agent - Legacy AMSv2 policies page
        • Access Manager Agent - Password settings page
        • Access Manager Agent - Devices page
        • Access Manager Agent - Groups page
      • Directory Configuration
        • Active Directory configuration page
          • Microsoft LAPS configuration page
          • Lithnet LAPS configuration page (Active Directory)
          • Just-in-time access configuration page
          • BitLocker configuration page
        • Microsoft Entra configuration page
      • Authorization Rules
        • Computer authorization rules page
        • Role authorization rules page
      • Effective access page
    • Getting Support
Powered by GitBook
On this page
  • Step 1: Enable agent support on the AMS server
  • Step 2: Deploy the Access Manager agents
  • Step 3: Configure Access Manager Agent policy
  • Step 4: Configure RapidLAPS scenarios
  • Step 5: Configure prompts for user input
  • Step 6: Create computer authorization rules for RapidLAPS
  • Step 7: Validate access

Was this helpful?

  1. Configuration
  2. Deploying Features

Setting up RapidLAPS

PreviousDeploying FeaturesNextLAPS

Last updated 4 months ago

Was this helpful?

This guide will walk you through configuring RapidLAPS in your environment.

RapidLAPS integrates into the Windows login screen and admin consent prompts, allowing you to speed up the process when using the LAPS password.

With RapidLAPS, by simply scanning a QR code, or visiting the Access Manager web app and entering a PIN, you can remotely authorize and log into any LAPS-enabled computer without ever knowing the LAPS password. Once authorized, Access Manager securely transports the LAPS password between the server and the client, saving you from having to type out a long and complicated password.

Using RapidLAPS requires the Access Manager agent to be installed on your computers, but you do not need to configure the Access Manager agent to manage the LAPS password. RapidLAPS works whether you are using Windows LAPS, legacy LAPS, or the Access Manager agent to manage your LAPS passwords.

RapidLAPS is only available on .

Step 1: Enable agent support on the AMS server

Follow the steps in

Step 2: Deploy the Access Manager agents

Deploy the .

Step 3: Configure Access Manager Agent policy

AMS uses agent policies to configure the behavior of Lithnet Access Manager agents.

From the Access Manager agent/Agent policies/Windows policies page, find or create a policy that applies to the computers you want to enable RapidLAPS for.

See the guide on for more information on policy targeting and creation.

Step 4: Configure RapidLAPS scenarios

First, select which scenarios in Windows you wish to enable RapidLAPS.

Scenario
Description

Enable RapidLAPS for logins

When configured, this setting will add a "Login with RapidLAPS" tile to the Windows login screen, allowing login to the local administrator account via Access Manager.

Enable RapidLAPS for elevation

When configured, this setting will add an "Elevate with Lithnet RapidLAPS" tile to the Windows admin consent (UAC)() prompt, allowing elevation of applications, installers, and system actions with the local administrator account via Access Manager.

Step 5: Configure prompts for user input

Optionally, you can present users with a series of prompts whenever they login or elevate with RapidLAPS. Responses to these prompts are delivered to the server if a login or elevation is attempted, and are presented to the user authorizing the request in the Access Manager web app (as well as being stored in the audit log).

The following options are configurable for user prompts:

  • Usage scenarios: Configure whether the prompt is shown with RapidLAPS requests at either the login screen or during elevation.

  • Data type: The type of prompt

    • Text: A simple text-box

    • Multiline text: A text box with multiple lines for long-form responses

    • Drop-down list: A drop down box, where a user can select an option from a list

    • Checkbox: A simple checkbox

    • Label: A piece of text that will appear in the prompt window (e.g., for providing organization-specific guidance)

  • Helper text: An optional message presented alongside the prompt

  • Required: Whether the specific prompt is required

  • Text and Multiline text-specific fields

    • Minimum length: The minimum length of the text input; set to "0" to disable length requirements

    • Validation regex: An optional regular expression for validating text

    • Validation failure message: An optional message to present to users when the validation requirements are not met

  • Drop-down list-specific fields

    • List options: A list of options a user can select in the drop down

Step 6: Create computer authorization rules for RapidLAPS

Once the policy is configured, you can now configure individual users and groups who can approve RapidLAPS logins or elevations using the AMS configuration tool.

From the Authorization rules/Computers page, select Add... to create a new authorization rule. Select the container containing the computers you wish to allow RapidLAPS access to, and provide a friendly description for this rule. This will appear in audit logs if a user is approves or denies a request.

Select Edit Permissions... to open the ACL editor. Assign the appropriate users and groups permission to allow RapidLAPS login and/or elevation approval access.

If you'd like to be notified when someone requests RapidLAPS login or elevation, select the notification channels you'd like to send to for success and failure events.

Step 7: Validate access

Once the policy has had time to propagate to the device, you can begin the validation process. If the policy has been processed, on the login screen, you will see a Login with RapidLAPS tile on the bottom left corner of the screen.

Select the tile and click the arrow to login with RapidLAPS. If you have configured any user prompts, complete them on the following page and click Submit. The QR code will appear which you can scan with a mobile device, or visit the AMS web app using the URL shown, and enter the PIN.

Once you have authorized the request in the web app, the login should proceed as normal.

If the login process does not work, double check that you have followed the steps in this article, and see the for how to find the Access Manager server and agent logs to help understand and resolve the issue.

supported Windows operating systems
Enabling agent support on the AMS server
Access Manager agent to your devices
creating and managing policies
troubleshooting guide
!