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
  • JIT access group creation
  • JIT group mapping
  • JIT mode
  • Active Directory time-based membership
  • AMS scheduler-managed membership

Was this helpful?

  1. Help and support
  2. Application help pages
  3. Directory Configuration
  4. Active Directory configuration page

Just-in-time access configuration page

PreviousLithnet LAPS configuration page (Active Directory)NextBitLocker configuration page

Last updated 10 months ago

Was this helpful?

Lithnet Access Manager supports granting access to computers using a just-in-time access model.

The JIT model used by Lithnet Access Manager involves 3 processes.

  1. A group is created in AD to provide JIT access to a specific computer

  2. The group is added to the local administrators group of that computer

  3. When a user requests just-in-time access to a computer, they are added to this group, for a limited period of time.

The first process can be manged by AMS. It can be configured to automatically create groups for all computers in an OU.

The second process is managed by group policy preferences. GPP is configured to add the JIT group to the local administrators group of the computer.

Finally, the AMS service through its access request and authorization process, can add members to a group for a limited period of time.

JIT access group creation

You can use AMS to automatically create a JIT group for every computer in a given OU. Note this doesn't have to be done by AMS if you have another tool you wish to use to create groups.

Select Enable automatic JIT group creation and press the Add... button to create a new mapping. Once the mapping has been created, use the Delegate permission... button to generate a script that grants AMS the rights it needs to manage the JIT groups.

JIT group mapping

Computer OU

Select the container that contains the computers you want to create JIT groups for, and select if access manager should find computers that exist in all child containers, or just the container specified.

Group OU

Select the container that access manager should create the group objects within. If you want to clean up groups created for computers that have been deleted, then tick the delete groups... tick box. Note, any group found in this container that doesn't match an expected JIT group will be deleted. Do NOT select this option if the OU contains groups that are NOT created by AMS.

Group name template

Specify the name of the group that should be created. You must use the %computerName% placeholder somewhere in the name. If you use the template JIT-%computerName% then for a computer named PC1 AMS will create a group called JIT-PC1

Group type

Select the type of group to create. There is rarely a reason to change this from the default of domain local

The AMS service checks every 60 seconds for new computers in the domain, and will create a group for any new computers it finds. Once an hour, the service will do a full synchronization of groups and computers. Only at this time, will missing computers be detected, and groups deleted if the mapping is configured to do so.

Unix GID

If you intend to use JIT groups on Linux machines that are bound to Active Directory, you may require a gid attribute to be configured for your JIT groups.

If configured, Access Manager will compute a gid for the group like so:

  • The GID is computed as gid = rid + <offset>, where offset is configured to ensure the generated identifiers do not clash with existing identifiers in your environment.

  • The resulting gid will be placed in the AD attribute of your choosing on the group object (default: gidNumber).

When picking an offset, ensure that it is significantly large enough to prevent clashes with already-allocated gids in your environment.

JIT mode

Based on the capabilities of your Active Directory domain, Access Manager can enable JIT support through two different mechanisms. Active Directory time-based membership and the AMS scheduler-managed membership.

Active Directory time-based membership

Time-based membership is the superior option, as it leverages the Privileged Access Management (PAM) feature in Active Directory. This allows AMS to add the user to the JIT group, with a time limit on that membership. Once that limit expires, the membership is automatically removed by AD itself.

The key feature of this mode, is that the Kerberos ticket the user obtains will only last as long as the group membership. Combined with membership in the Protected Users group, you can be assured that the user's access will expire precisely when then group membership expires. However, time-based membership requires enabling the AD Privileged Access Management feature, which is only supported on Windows Server 2016 and later forest functional levels.

AMS scheduler-managed membership

AMS scheduler-managed membership is supported in all Windows Server 2003 and later domains. AMS will add the user to the group, and created a scheduled job internally to remove the user at the time the membership expires. Unlike the time-based membership option, the group expiry is not linked to the lifetime of the Kerberos ticket, so users may not lose access immediately.

This list shows each domain and forest known to the AMS server, and the type of JIT it supports based on the forest functional level.

Forest

Shows the name of the forest

Domain

Shows the name of the domain

Forest Functional Level

Shows the current functional level of the forest

Domain Functional Level

Shows the current functional level of the domain

PAM Status

Shows the availability of the AD PAM feature in this domain

  • Not supported: The forest functional level does not support PAM.

  • Supported, but not enabled: The forest functional level supports PAM, but it has not been enabled.

  • Enabled: The PAM feature is enabled and available in the domain.

JIT Type

The JIT type is always based on the availability of the PAM feature in the domain. If it is enabled, the JIT type will always be the preferred time-based membership mode. If it is not enabled, or not available at all, the JIT type will fall back to AMS scheduler

In the instance where your Active Directory domain has been configured with the components, Access Manager can generate gidNumber attributes for JIT groups, such that they are visible by Unix machines.

The group will be created in Active Directory, and the is retrieved.

The domain-unique is extracted from the SID.

This may not be required if your Linux/AD binding makes use of automatic ID mapping. For example, can be configured to automatically map Active Directory security identifiers (SIDs) to POSIX-style .

Identity Management for UNIX
security identifier (SID)
relative identifier (RID)
SSSD
uid and gid identifiers