Create temporary accounts with JIT provisioning
Just-in-time (JIT) provisioning keeps privileged accounts usable only for the duration of a task or session. The JIT account mode of a PAM account determines what happens to the account at checkout and check-in.
None
The account stays as-is before and after the session.
Create the account on checkout
A temporary account is created in Active Directory at checkout and automatically deleted at check-in. Available for Domain user PAM accounts only.
Enable account on checkout
An existing account is enabled at checkout and disabled at check-in. Available for Domain user and Entra ID User PAM accounts.
This guide explains how to configure both modes.
Create the account on checkout
Configure JIT account creation
Go to Administration – Privileged access management (PAM) – Providers.
Click the name of your Domain user provider, or click its Edit button.
Select JIT privilege elevation and locate the Advanced section.
Enter the path in the correct format for your Active Directory (e.g.,
OU=JITAccounts,DC=example,DC=com) under JIT account creation location.Click Update.
Go to Administration – Privileged access management (PAM) – Providers.
Click the name of your Domain user provider, or click its Edit button.
Select the JIT privilege elevation tab.
Enter the path in the correct format for your Active Directory (e.g.,
OU=JITAccounts,DC=example,DC=com) under JIT account creation location.Click Update.
Go to Administration – Privileged access management (PAM).
Select the Providers tab.
Select your Domain user provider and click Edit.
Select JIT privilege elevation and locate the Advanced section.
Enter the path in the correct format for your Active Directory (e.g.,
OU=JITAccounts,DC=example,DC=com) under JIT account creation location.Click Save.
Add a new domain user PAM account
Go to your PAM vault and click Add (+).
Select PAM – Domain user, then click Continue.
Fill in Name.
Select your Provider.
Fill in Username.
Under JIT account mode, select Create the account on checkout.
Click Add.
Go to your PAM vault and click Add (+).
Select Accounts – Domain user, then click Continue.
Fill in Name.
Select your Provider.
Fill in Username.
Under JIT account mode, select Create the account on checkout.
Click Add.
In your PAM vault, right-click a folder in the navigation pane and select Add entry.
Select Privileged access management (PAM) – Domain user, then click Select.
Fill in Name.
Select your Provider.
In the General tab, fill in Username.
Under JIT account mode, select Create the account on checkout.
Click Save.
Understand the JIT process
When you check out the account, the system automatically creates it in Active Directory. It remains active for the duration of the checkout period, and upon check-in, the account is immediately deleted from Active Directory.
Enable account on checkout
This mode keeps an existing account in the directory between checkouts instead of creating and deleting it.
Set the JIT account mode
Add a new Domain user or Entra ID User PAM account as described above, or edit an existing one:
Right-click the PAM account and select Properties.
Go to General.
Under JIT account mode, select Enable account on checkout.
Click Update.
Open the PAM account and click Edit.
Go to General.
Under JIT account mode, select Enable account on checkout.
Click Update.
Right-click the PAM account and select Properties.
Go to General, then select the General tab.
Under JIT account mode, select Enable account on checkout.
Click Save.
Understand the enable and disable process
At checkout, the account is enabled in Active Directory or Entra ID. If JIT privilege elevation groups are granted with the checkout, they are added once the account is enabled. If granting the groups fails, the account is disabled again.
At check-in, the account is disabled and the JIT privilege elevation groups are revoked. The account is always disabled at check-in, even if it was enabled before the checkout.
Heartbeat behavior
For an account in Enable account on checkout mode, the expected state outside a checkout is disabled:
If the account is disabled, the heartbeat treats it as the expected state.
If the account is enabled while it is not checked out, the heartbeat fails with The account is still enabled.
For a disabled Domain user account, the heartbeat can only verify the stored password when the provider connects with LDAPS, and fails if the password no longer matches. Otherwise, it only confirms that the account exists in the directory.
Last updated
Was this helpful?