Description:
Goverlan now supports remote authentication using Azure AD credentials. Customers may now use Azure AD accounts with administrative access to use all Goverlan’s remote management features.
How to use:
Goverlan can use your Azure AD credentials automatically without the need for additional local credentials.
Alternatively, you may also use the Goverlan Credential Manager to store Azure AD credentials if necessary. For more information on using the Goverlan Credential Manager, see Using Alternate Credentials (goverlan.com)
Whenever an Azure AD Credential is needed you must use the AzureAD\ domain component:
For example,
Requirements:
The following requirements must be met to use Azure AD Authentication with Goverlan.
- Both Systems must be in the same AzureAD Domain.
- Goverlan Console version 10.1.3.1172 and agent version 10.1.3 and above are required to use Azure AD Authentication with Goverlan.
- The PKU2U protocol must be enabled on both the Console and Agent side systems.
- PKU2U can be enabled through Group Policy via the following path:
- Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options
Permission Requirements:
For Administrative Access to Azure AD Joined Devices, the following configurations are required:
- The Goverlan Operator must have the Azure AD Device Administrators or Global Administrators Role
- The remote device have an Azure AD status of Azure AD JOINED.
Where to get it:
Log in to https://my.goverlan.com with your Goverlan account. Select the CONSOLE tab and click Downloads for this product.
Click Stable Build to get 10.1.3
Push out the updated agents to your systems. For more information about agent management. See The Goverlan Agent Manager.