Lithnet Access Manager
PricingRequest a trial or quoteDownloads
v2.0
v2.0
  • Home
  • What's new in Access Manager v2
  • How does Lithnet Access Manager help prevent lateral movement?
  • Access Manager Editions
  • Licensing
  • Change log
  • Installation
    • Getting started
    • System Requirements
    • Downloads
    • Upgrading from Access Manager v1
    • 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 Access Manager in a Failover Cluster
    • Installing the Access Manager Agent
      • Choosing between the Microsoft and Lithnet agents for LAPS support
      • 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 Azure AD
      • Setting up authentication with Okta
      • Setting up smart card authentication
      • Setting up integrated windows authentication
    • Deploying Features
      • Setting up Microsoft LAPS for Active Directory
      • Setting up Microsoft LAPS for Azure Active Directory
      • Setting up Lithnet LAPS
        • Preparing the AMS directory
        • Setting the AMS directory for Lithnet LAPS clients
        • Setting up Lithnet LAPS for Azure AD joined and registered devices
        • Setting up Lithnet LAPS for domain-joined devices
        • Setting up Lithnet LAPS for macOS and Linux
        • Setting up Lithnet LAPS for standalone Windows devices
      • Setting up BitLocker access
      • Setting up JIT for computers
      • Setting up JIT for roles
    • 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
      • Importing rules from the Lithnet LAPS web app
      • 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 Azure Active Directory
    • 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
    • Advanced help topics
      • 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
    • PowerShell reference
      • Add-AmsDeviceRegistrationKeyGroup
      • Add-AmsGroupMember
      • Export-AmsServerDiagnostics
      • Get-AmsActiveDirectoryJitOptions
      • Get-AmsComputerAuthorizationRule
      • Get-AmsDevice
      • Get-AmsDeviceRegistrationKey
      • Get-AmsGroup
      • Get-AmsGroupMembers
      • Get-AmsHostConfig
      • Get-AmsJitSchedulerJob
      • Get-AmsLocalAdminPassword
      • Get-AmsLocalAdminPasswordHistory
      • Get-AmsRoleAuthorizationRule
      • New-AmsComputerAuthorizationRule
      • New-AmsDeviceRegistrationKey
      • New-AmsGroup
      • New-AmsRoleAuthorizationRule
      • Remove-AmsComputerAuthorizationRule
      • Remove-AmsDevice
      • Remove-AmsDeviceRegistrationKey
      • Remove-AmsDeviceRegistrationKeyGroup
      • Remove-AmsGroup
      • Remove-AmsGroupMember
      • Remove-AmsJitSchedulerJob
      • Remove-AmsRoleAuthorizationRule
      • Set-AmsActiveDirectoryJitOptions
      • Set-AmsComputerAuthorizationRule
      • Set-AmsDevice
      • Set-AmsDeviceRegistrationKey
      • Set-AmsGroup
      • Set-AmsHostConfig
      • Set-AmsRoleAuthorizationRule
    • Application help pages
      • Access Manager Directory configuration page
      • Access Manager Directory Devices page
      • Access Manager Directory Groups page
      • Lithnet LAPS configuration page (Access Manager Directory)
      • Access Manager Directory Registration Keys page
      • Lithnet LAPS configuration page (Active Directory)
      • Microsoft LAPS configuration page
      • Active Directory configuration page
      • Auditing page
      • Authentication configuration page
      • Computer authorization rules page
      • Role authorization rules page
      • Azure Active Directory configuration page
      • BitLocker configuration page
      • Database configuration page
      • Effective access page
      • Email configuration page
      • IP Address detection configuration page
      • Just-in-time access configuration page
      • Licensing configuration page
      • Rate limit configuration page
      • Host configuration page
      • User interface configuration page
      • Security page
    • Getting Support
Powered by GitBook
On this page
  • Summary
  • Cause
  • Resolution
  • Deployment script
  • Further reading

Was this helpful?

  1. Help and support
  2. Support Articles

KB000008: AMS is unable to JIT into privileged groups such as Domain Admins

PreviousKB000007: Adding JIT groups via Group Policy doesn't work with NTLM DisabledNextAdvanced help topics

Last updated 10 months ago

Was this helpful?

Summary

When attempting to JIT into a privileged group such as Domain Admins, the request may fail and show the user the following error message.

An unexpected error occurred while trying to complete your request

The access-manager-webapp.log file will show a message similar to the following

System.UnauthorizedAccessException: Access is denied.
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.SetInfo()
at System.DirectoryServices.DirectoryEntry.CommitChanges()
at Lithnet.AccessManager.ActiveDirectory.ActiveDirectoryGroup.AddMember(IActiveDirectorySecurityPrincipal principal, TimeSpan ttl)

There may be one or more successful attempts before these errors occur.

Cause

Certain groups in Active Directory are considered by Active Directory.

Protected groups have a special permission set on them enforced by AD itself. Every 60 minutes AD will turn off inheritance and reset the ACL of these protected users and groups, if they have been modified.

The process that does this also follows nested membership. So if you add a group to domain admins, that group also becomes protected, and has its ACL overwritten to the AdminSDHolder template.

The ACL template that is applied comes from the AdminSDHolder template in AD.

Resolution

In order to allow Access Manager to modify the member of protected groups, you must modify the ACL of the AdminSDHolder object, to include the AMS service account. This does have the side effect that the AMS service account will have the access you provided, to all protected accounts and groups.

There is no way to limit the permission to a specific group.

To do this safely, we recommend having a dedicated AMS instance for 'tier zero', where the underlying server, and the AMS instance is only accessible by Domain admins. This instance is then used for JITting into roles like schema admins, enterprise admins, etc.

Deployment script

The following script can be used to grant 'write member' permissions to all protected groups in a domain, by modifying the AdminSDHolder template permissions in the directory.

# Grant-ModifyProtectedGroupMembershipPermissions
# 
# This script grants permissions for the AMS service account to update protected groups
# Running this script requires membership in the Domain Admins group for the target domain
#
# Version 1.0

#-------------------------------------------------------------------------
# Set the following values as appropriate for your environment. If the service account is in another forest and cannot be resolved, provide its SID, by looking it up first in the source domain using Get-ADUser or Get-ADServiceAccount
#-------------------------------------------------------------------------

$amsServiceAccount = "dev\svc-lithnetams$"

#-------------------------------------------------------------------------
# Do not modify below here
#-------------------------------------------------------------------------

if (-not $amsServiceAccount.StartsWith("S-1-5"))
{
    $ntaccount = new-object System.Security.Principal.NTAccount $amsServiceAccount
    $sid = $ntAccount.Translate([System.Security.Principal.SecurityIdentifier]);
}
else
{
    $sid = $amsServiceAccount
}

Import-Module ActiveDirectory

$ErrorActionPreference = "Stop"
$InformationPreference = "Continue"

if ([string]::IsNullOrEmpty($domain))
{
	$server = (Get-ADRootDSE).dnsHostName
}
else
{
	$server = (Get-ADDomainController -DomainName $domain -Discover -ForceDiscover -Writable).HostName[0]
}

$rootDSE = Get-ADRootDSE -Server $server

if ([string]::IsNullOrEmpty($DN))
{
	$DN = $rootDSE.defaultNamingContext
}

$DN = "CN=AdminSDHolder,CN=System," + $DN 

$schemaNC = $rootDSE.schemaNamingContext
$groupObjectGuid = New-Object Guid @(,(Get-ADObject -Server $server -SearchBase $schemaNC -LdapFilter "(&(ldapDisplayName=group)(objectclass=classSchema))" -Properties "SchemaIDGuid").SchemaIDGuid)
$memberAttributeGuid = New-Object Guid @(,(Get-ADObject -Server $server -SearchBase $schemaNC -LdapFilter "(&(ldapDisplayName=member)(objectclass=attributeSchema))" -Properties "SchemaIDGuid").SchemaIDGuid)

$ntaccount = new-object System.Security.Principal.NTAccount $amsServiceAccount
$sid = $ntAccount.Translate([System.Security.Principal.SecurityIdentifier]);

$ace1user = new-object System.DirectoryServices.ActiveDirectoryAccessRule $sid, "WriteProperty", "Allow", $memberAttributeGuid, "None", $groupObjectGuid
 
$path = "AD:\$DN"

$acl = get-acl -Path $path
$acl.AddAccessRule($ace1user)

set-acl -AclObject $acl -Path $path

Further reading

  • https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/plan/security-best-practices/appendix-c--protected-accounts-and-groups-in-active-directory

  • https://specopssoft.com/support/en/password-reset/understanding-privileged-accounts-and-adminsdholder.htm

If you grant write member permissions to the AMS service account on the AdminSDHolder template, then AMS will have modify member rights on .

'protected' groups
all groups that are protected