JIT Domain Log In (BETA)
Understanding how to setup JIT domain login
Table of Contents
Overview
Just-in-Time (JIT) Domain Log In in AutoElevate enables technicians to securely authenticate into Active Directory domains using temporary privilege elevation, eliminating the need for persistent admin credentials. This feature improves security posture by enforcing least-privilege access while maintaining operational efficiency for support teams.
What is JIT Domain Log In?
Feature Description
JIT Domain Log In allows technicians to request and receive temporary domain access using controlled authorization workflows. Instead of using static domain admin accounts, the system dynamically provisions and manages domain user privileges during the login session.
Key capabilities include:
- Temporary domain user creation tied to the technician
- Role- and group-based authorization controls
- Mobile device approval workflows
- Automatic privilege downgrade after login
Why It Matters
- Eliminates persistent domain admin credentials
- Reduces risk of credential theft or lateral movement
- Provides full audit visibility of privileged access
- Aligns with Zero Trust and least privilege security models
Platform-Specific Configuration & Usage
Admin Portal Configuration
Enable JIT Domain Log In
- Navigate to Settings → Configuration
- Enable the Domain Log In feature
- Ensure appropriate permissions are assigned to administrators
Configure Authorizations
- Define which:
- Domains are included
- Users/roles can approve requests
- Groups or OUs can be selected during login
- Multiple authorization rules can apply simultaneously (additive model)

Device Authorization Setup
- Generate the Certificate Authority (CA) from the portal
- Enter a Name for the Certificate Authority
- Enter a very strong password
- Confirm the password

- Click Generate to download both: ***DO NOT RENAME THESE FILES***
- Public Key (installed on Domain Controller)
- Private Key (stored securely for approvals)
Enable Multiple Downloads in chrome
By default, Chrome will only allow single-file downloads, so you'll need to allow multiple-file downloads for AutoElevate
- In the Chrome address bar, go to chrome://settings/content/automaticDownloads
- Click Add next to Allowed to automatically download multiple files
- Enter msp.autoelevate.com
- Approve technician mobile devices using the secure seed + verification flow
- Copy the downloaded private .json file
- Enter the password used in the above step
- Click the unlock certificate button

- Click approve next to the device you want to approve for JIT Domain login
- Provide the seed word to the agent to use in registering the device

- From the mobile device, click the hamburger menu and select Enable JIT Log In

- Enter the seed word
- Provide the verification code to the admin

- Enter the verification code for the seed word and click Approve

- Click Save
- On the Mobile device, click Check for Approval
- Mobile device should indicate Device is Ready for JIT Domain Log In

Domain Controller (Server-Side Setup)
Install Certificate Authority
- Ensure the AutoElevate agent is installed on at least one Domain Controller
- Create directory: C:\Program Files (x86)\AutoElevate\certificates
- Place the Public Key file (.PEM) in this directory

Requirements
- At least one Primary Domain Controller must run the AutoElevate agent
- Domain availability appears only after agent reporting begins
Login Workflow
- From the server login screen
- Click the Just In Time Admin Login User
- Click the Begin Just-in-Time Login…

- You should be presented with a QR code

- Using the AutoElevate Mobile app
- Select the Scan barcode Icon
- Scan the JIT QR code
- Select Domain Group or OU
- Click Submit Just-in-time Log In Request
- Select the Scan barcode Icon

- Use Strong biometric authentication to complete the domain login
Mobile App (iOS / Android)
Device Approval
- Devices must be explicitly approved before use
- Approval requires:
- Private key unlock
- Seed exchange
- Verification code validation
Security Requirements
- Strong biometric authentication required
- Minimum OS versions:
- Android 12+
- iOS 5.1+
Advanced Use Cases
Secure MSP Operations
Grant technicians domain access across multiple tenants without sharing credentials
Just-in-Time Privileged Access
Allow temporary access for specific tasks, such as AD changes or troubleshooting
Granular OU-Based Access Control
Restrict technicians to only specific organizational units
Compliance & Audit Readiness
Maintain detailed logs of who accessed domain resources and when
Best Practices
- Store Private Key files securely and restrict access
- Use role-based authorizations instead of individual user assignments
- Limit access scope to specific OUs whenever possible
- Enforce biometric authentication on all mobile devices
- Regularly review authorization configurations
- Ensure Domain Controllers have consistent agent deployment
Troubleshooting
Issue: Logon Failure – User Not Granted Logon Type
Error Example:
Logon failure: the user has not been granted the requested logon type
Resolution:
- Open
secpol.msc - Navigate to:
Local Policies → User Rights Assignment - Update Allow log on locally to include required users [JIT Domain...e Bulletin | Confluence]
Issue: Domain Not Appearing in Authorization Settings
- Confirm the Domain Controller agent is installed and reporting
- Allow time for initial state sync
Issue: Mobile Device Cannot Approve Requests
- Ensure the device has been approved using the correct private key
- Verify biometric authentication is enabled
- Confirm correct user context (approval is user-specific per device)
Issue: Connectivity Failures
- Ensure outbound access to:
- Check firewall or proxy restrictions
Security & Sync Behavior
- Temporary domain users are reused per technician, but do not retain admin privileges after login
- Privileges are automatically downgraded post-session
- Certificate Authority files are NOT stored by AutoElevate — customers are responsible for secure storage
- Mobile approvals are tied to both the device and the user
- Multiple public keys can exist on Domain Controllers for redundancy