Certificate-based Trusted Endpoint verification for Active Directory DS will reach end-of-life in a future release. Migrate existing Active Directory Domain Services Certificate Deployment management integrations to Active Directory with Device Health. Learn more about the end-of-life timeline and migration options in the Duo Trusted Endpoints Certificate Migration Guide.
Duo's Trusted Endpoints feature secures your sensitive applications by ensuring that only known devices can access Duo protected services. When a user authenticates via the Duo Prompt, we'll check for the presence of the Duo Device Health app or a Duo device certificate on that endpoint. You can monitor access to your applications from trusted and untrusted devices, and optionally block access from unmanaged, untrusted devices.
Trusted Endpoints is part of the Duo Beyond plan.
Ensure you have the following access and privileges:
This integration relies on having the Duo Device Health app present on your Active Directory (AD) domain-joined Windows endpoints. When users authenticate to applications protected with Duo's browser-based prompt, Duo matches the domain information reported by Device Health app with the management integration configuration.
The Windows client systems must be directly joined to the Active Directory domain that you specify (via SID) during Active Directory with Device Health configuration for trusted status confirmation.
The logged-in Windows user must be a domain account from the Active Directory domain that you specify (via SID), or trust verification during Duo authentication will fail.
Deploy the Duo Device Health application to your Windows endpoints. Refer to the Duo Device Health documentation to learn about different options for deploying the application.
Note that you do not need to configure a Device Health policy in order to use Active Directory Domain Services with the Device Health app for endpoint verification.
The new Active Directory with Device Health integration is created in the "Disabled" state. You'll turn it on when you're ready to apply your Duo trusted endpoints policy.
Keep the Admin Panel open in your browser to complete the next steps of obtaining your domain information and providing it to the Duo management integration.
Log in to a domain controller or other Windows system with the RSAT package installed.
Launch PowerShell and paste in this cmdlet string:
(Get-ADDomain | Format-Table -Property DomainSID -HideTableHeaders | Out-String).Trim() | clip
This obtains the security identifier (SID) value for your AD domain and copies it to your clipboard automatically. You shouldn't see any output in the PowerShell window.
If you receive an error message stating "The term 'Get-ADDomain' is not recognized as the name of a cmdlet, function, script file, or operable program" then the ActiveDirectory PowerShell module may not be installed on the system where you ran the command. Install RSAT or locate a different system that has the module installed.
Return to the Active Directory with Device Health management integration in the Admin Panel and paste in the copied domain SID in the field provided. It will look similar in format to
At this point the configured integration is disabled and applies to no users until you finish your deployment
If you have endpoints in multiple domains with which you'd like to perform management verification with Device Health, create a new Device Health with Active Directory management integration for each domain, and configure each management integration with the unique SID for each domain. This also applies to child domains in a forest or external trusted domains.
Once your managed computers have Duo Device Health installed, you can update the Trusted Endpoints policy to start checking for management status as users authenticate to Duo-protected services and applications.
When your trusted endpoints policy is applied to your Duo applications, return to the Active Directory with Device Health management integration in the Admin Panel. The "Change Integration Status" section of the page shows the current integration status (disabled by default after creation). You can choose to either activate this management integration only for members of a specified test group or groups, or activate for all users.
The Device Insight and Endpoints pages in the Duo Admin Panel show trusted and untrusted access device status.
As more of your devices have Duo Device Health installed you can change the integration activation to apply to all users (if you just targeted test groups before), adjust your trusted endpoints policy to expand the target group, apply it to additional protected services, or start blocking access to applications from devices that do not pass the managed endpoint check. See the Trusted Endpoints documentation for more information.
Deleting a trusted endpoints Device Health with Active Directory management tool integration from the Duo Admin Panel immediately prevents identification of domain-joined devices from that configured domain using Device Health. Be sure to unassign your trusted endpoints policy from all applications or remove the "Trusted Endpoints" configuration item from your global policy before deleting an existing Device Health with Active Directory integration from "Trusted Endpoints Configuration". Leaving the policy settings in place after deleting a management tools integration may inadvertently block user access to applications.
If you also have a legacy AD DS certificate-based management integration system configured, deleting the new Active Directory Domain Services integration that uses Device Health does not invalidate any certificates issued by the legacy AD DS integration.
Leaving the policy settings in place after deleting a management tools integration may inadvertently block user access to applications.
Before enabling the Trusted Endpoints policy on your applications, you'll need to deploy the Duo device certificate to your managed devices. This guide walks you through using Active Directory Domain Services (AD DS) and Group Policy Objects (GPOs) to enable automatic certificate enrollment on your domain-joined Windows computers.
Certificate-based Trusted Endpoint verification using Active Directory will reach end-of-life in a future release. Consider migrating your certificate-based AD integration to Active Directory with Device Health. Use of the Duo Device Health app for trust attestation provides several advantages over the use of device certificates:
These instructions remain available for customers who created Active Directory certificate integrations before August 2021 and may need to reconfigure or recreate them. Duo continues to support existing AD certificate deployments and will do so until the integration reaches end-of-life status in a future update.
Log in to the Duo Admin Panel and view the details of your existing Active Directory Domain Services integration. Keep this open in your browser to complete the next steps of installing the Duo Certificate Proxy in your AD environment and creating GPOs to update your client configuration.
Provision a host server then install and configure the Duo Certificate Proxy.
Set up a Windows server to host the Duo Certificate Proxy and join it to the same AD domain as the users and computers who will be authenticating from trusted endpoints. Do not install on a domain controller or an Enterprise PKI.
The minimum system requirements for the Duo Certificate Proxy are:
Apply all critical and important updates to the server from Windows Update, including the .NET Framework 4.5.2.
If deploying the Duo certificate proxy on Windows 2012 R2, install the Windows 10 Universal C Runtime (CRT) on the server. Skip this step if deploying on Windows 2016.
If the server is running a local firewall, you'll need to open up TCP ports 135 and 1024-65535 for DCOM and RPC inbound access from your domain computers to the Duo Certificate Proxy. Here's how to permit access to these ports in the Windows Firewall:
Verify that the new Windows Firewall inbound rule is enabled.
If you have blocked HTTP access on TCP port 80, you should also open that up to the certificate proxy destination server before proceeding.
Log on to the server as a domain user who is a member of both the Domain Admins and Enterprise Admins groups. If you were added to either of those groups during your current logon session then you need to log out and back in for your new privileges to take effect.
Download and launch the Duo Certificate Proxy installer (view checksums for Duo downloads here). Follow the on-screen prompts to install the application. Specify the destination folder (the default location is
C:\Program Files\Duo Security\Duo Certificate Proxy\).
Leave the Launch Duo Certificate Proxy Wizard option checked on the final screen of the installer, and click Finish. The Duo Certificate Proxy wizard opens automatically.
The wizard verifies that you are an AD enterprise and domain admin when you click Next on the welcome page.
Switch to your Duo Admin Panel browser window, open to the "Active Directory Domain Services" management tools integration. Click to view the secret key in the "Install the Duo Certificate Proxy" section of the page (step 2), and then select and copy the revealed secret key to your clipboard.
Return to the Duo Certificate Proxy Wizard and paste the secret key you just copied from the Admin Panel into the "Paste secret key here" box. Click Next.
Choose the certificate type (or types) you wish to deploy, based on the certificate lifetimes you want used in your environment.
|Long-lived certificates||These certificates expire one year from issuance. This is the best option for most Duo deployments.|
|Short-lived certificates||These certificates expire one week (seven days) from issuance. Select this option when you have users who need certificates reissued more frequently than the one year default. For example, you have virtual desktop users whose VDI endpoints are redeployed periodically, or a group of contractors who aren't expected to use the same workstations for a year.|
|1 Day certificates||These certificates expire one day after they're issued. Typically this option is used for testing trusted endpoints verification, and shouldn't be used for production.|
You can select one or multiple certificate types, and assign your selected certificate types to different user groups in the next step.
Specify the AD group or groups containing the users who will receive the Duo certificate for each type of certificate you selected in the next step. When piloting trusted endpoints in your environment we recommend targeting a group of test users during initial configuration. You can return to the Duo Certificate Proxy configuration wizard later to add additional groups after verifying certificate enrollment and trusted endpoint reporting and access for the test group.
Either click the Select button and type in all or part of an AD domain group, or type in the full name of the AD target group directly into the configuration wizard and click Validate to check the group name against AD. To specify more than one group separate the group names with a comma (without any spaces before or after the comma).
Click Next after validating the domain group name(s).
If you enabled more than one certificate type (e.g. both long-lived and short-lived), repeat the group selection operation for each certificate type.
Note that you may not assign different certificate types to the same AD group.
Pick the trust configuration method. If your organization has an existing PKI OR if you have Windows 10 or Windows Server 2016+ clients that you plan to verify as Duo trusted, select the Trust the Duo root option. If no public key infrastructure (PKI) exists in your environment (such as Active Directory Certificate Services) and no Windows 10 or Server 2016+ systems will authenticate as Duo trusted endpoints, select the first option Install Duo root certificate as untrusted.
Do not choose the Manual setup of Duo root option without first contacting Duo Support.
Double-check your selected certificate types, domain group assignments, and trust configuration. If everything looks correct, click Confirm.
You've completed the initial Duo Certificate Proxy configuration. Exit the wizard and proceed to Group Policy configuration.
Create a new Group Policy object (GPO) for Duo certificate deployment and browser configuration, and then apply the new GPO to target users. For additional information about using GPOs, please see Microsoft's Group Policy documentation collection.
On your domain controller or another system with the Windows Remote Server Administration Tools installed, launch the Group Policy Management console (GPMC).
Expand your forest and navigate down the tree to Group Policy Objects. Right-click the Group Policy Objects folder and click New. Enter a name for the new GPO (such as "Duo Certificate Policy") and click OK.
Right-click the new GPO created in step 2 and click Edit.
To enable automatic retrieval of the Duo device certificate by domain clients, navigate to User Configuration\Policies\Windows Settings\Security Settings\Public Key Policies and double-click Certificate Services Client - Auto-Enrollment in the right pane of the policy editor.
On the "Enrollment Policy Configuration" settings tab, set the "Configuration Model" to Enabled and enable both the Renew expired certificates, update pending certificates, and remove revoked certificates and Update certificates that use certificate templates options.
Click OK to close the Auto-Enrollment properties window.
To enable automatic selection of the Duo certificate by Internet Explorer on the client endpoints, navigate to User Configuration\Preferences\Windows Settings\Registry.
[hkcu_v2.xml](https://dl.duosecurity.com/hkcu_v2.xml) (4 kb) and [hklm_v2.xml](https://dl.duosecurity.com/hklm_v2.xml) (4 kb)
Return to the Group Policy editor window. Copy the downloaded hkcu_v2.xml XML file (from an Explorer window — not the file contents) and paste it into the "Registry" pane on the right of the GPO editor window. When asked if you are sure you want to import the pasted document, click Yes.
This adds registry settings under the following keys to the GPO:
These registry values allow Internet Explorer and Edge to automatically select the Duo device certificate when requested by the Duo browser prompt. If you don't push these registry settings to your Windows clients, then Internet Explorer prompts users to manually select the Duo certificate during authentication.
Copy and paste the downloaded hklm_v2.xml XML file (from an Explorer window — not the file contents) into the "Registry" pane on the right of the GPO editor window. Confirm import of the pasted document by clicking Yes.
This adds registry settings under the following keys to the GPO:
These registry values let Internet Explorer, Edge Chromium, and Chrome automatically select the Duo device certificate when requested by the Duo browser prompt without prompting the user interactively to select the certificate.
When you've finished configuring all settings, close the Group Policy editor window.
Click the Delegations tab of the new Duo certificate GPO, and then click the Advanced button in the lower right corner.
Click the Add... button on the "Security" tab. Enter Domain Computers in the "Select Users, Computers, Service Accounts, or Groups" dialog, and click OK.
Click on the Domain Computers group in the "Group or user names" list to select it. In the "Permissions for Domain Computers" area in the bottom half of the security settings window check the boxes for Read and Apply group policy in the "Allow" column. Click OK.
The default GPO security filtering applies the new policy to all domain authenticated users. Restrict this new GPO so that it applies to only members of the domain group(s) you specified during Duo Certificate Proxy configuration.
Click the Scope tab of the new Duo certificate GPO. In the "Security Filtering" section, click Authenticated Users to select and then click Remove.
Next, click the Add button under "Security Filtering". Select the same domain group(s) you selected on the "Select AD Group" page of the Duo Certificate Proxy configuration wizard and click OK. Those groups are added to the "Security Filtering" list alongside the Domain Computers group.
The final step is linking the policy. Right-click on your domain in the left side of the GPMC console and select Link an Existing GPO.... Select the new Duo certificate GPO in the list of Group Policy objects and click OK. The "Links" section of the GPO's "Scope" tab shows the linked locations.
Exit the Group Policy Management Console.
Confirm that the Duo Certificate Proxy is working by manually applying the Duo GPO settings on an endpoint.
Log on to a domain-joined client PC as a member of the pilot group specified during the Duo Certificate Proxy group selection and in the Duo certificate GPO scope.
Open a command prompt window and type in this command:
After the policy update completes, type in this command:
In the gpresult output, look for the your new Duo GPO in the "Applied Group Policy Objects" list.
If the Duo certificate enrollment GPO was successfully applied, check that the Duo certificate was successfully obtained via the Duo Certificate Proxy server. In the same command prompt window where you ran gpresult, type in this command:
Expand Certificates - Current User\Personal\Certificates. Look for the Duo Device Authentication certificate in the list.
Finally, verify the Chrome and Internet Explorer registry changes from the GPO. In the same command prompt window where you ran gpresult, type in these commands to check for the new IE and Chrome settings.
reg query "HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\1" reg query HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\AutoSelectCertificateForUrls
You should see the information highlighted in the image below.
Once your domain users' computers apply the new certificate GPO settings and receive the Duo certificate you can configure the Trusted Endpoints policy to start checking for the certificate as users authenticate to Duo-protected services and applications. The Device Insight and Endpoints pages in the Duo Admin Panel show which access devices have the Duo certificate present.
Return to the Active Directory Domain Services management integration in the Duo Admin Panel and click the Activate button at the bottom of the page so that the Device Insight and Endpoints pages in the Duo Admin Panel show trusted and untrusted access device status.
As more of your devices receive the Duo certificate you can change the integration activation to apply to all users (if you just targeted test groups before), adjust your trusted endpoints policy to expand the target group, apply it to additional protected services, or start blocking access to applications from devices that do not have the Duo certificate. See the Trusted Endpoints documentation for more information.
If you expand your trusted endpoints rollout by targeting additional user groups (as opposed to adding new users to the groups selected during initial configuration), you'll also need to add those additional groups to the Duo certificate GPO scope and the Duo Certificate Proxy configuration.
To add additional groups to the GPO scope:
Launch the Group Policy Management Console (GPMC) and view the "Scope" tab of the Duo certificate GPO.
Click the Add button under "Security Filtering". Select the domain group(s) you want to add to the policy and click OK.
To add additional groups to the Duo Certificate Proxy:
Log on to the Duo proxy server as an enterprise and domain administrator.
Launch the Duo Certificate Proxy Configuration application from the Start Menu.
Proceed through the wizard to the "Select AD Group" page. Type in the additional group name or names, separating each with a comma. Click the Validate button to verify your input.
Continue moving through the configuration wizard. Confirm the group changes and exit the wizard after completing the update.
Deleting a trusted endpoints management tool integration from the Duo Admin Panel immediately invalidates issued Duo device authentication certificates. Be sure to unassign your trusted endpoints policy from all applications or remove the "Trusted Endpoints" configuration item from your global policy before deleting an existing AD DS integration from "Trusted Endpoints Configuration". You should also unlink or delete your auto-enrollment GPO in the Group Policy Management console.
Leaving the policy settings in place after deleting a management tools integration may inadvertently block user access to applications.
Need some help? Take a look at our Trusted Endpoints Knowledge Base articles or Community discussions. For further assistance, contact Support.