Products

Spotlight on remote PAM with AnyIdentity and Devolutions Gateway

Remote pam anyidentity devolutions gateway priviledged accounts management blog

The release of Devolutions Server 2024.3 introduced new flexibility for managing AnyIdentity provider scripts, allowing them to be executed remotely via a rewritten WinRM stack and Devolutions Gateway, providing secure, versatile options for privileged account management with Devolutions PAM across various environments.

Adam Listek

As an IT specialist with over 20 years in the industry, I work hard to stay up to date on new and emerging technologies. Having worked in diverse fields from healthcare to higher education, I love new challenges and creating in-depth content to share with the world!

View more posts

With the release of Devolutions Server (DVLS) 2024.3, managing AnyIdentity provider scripts has reached a new level of flexibility and control. AnyIdentity providers, which act as a bridge between Devolutions PAM and diverse identity systems, leverage PowerShell scripts to centralize privileged account management. Before the 2024.3 update, AnyIdentity provider scripts could only be executed on systems directly accessible to DVLS. However, many scenarios require running AnyIdentity PowerShell scripts on external network segments (such as MSP client networks or remote offices), using a set PowerShell version, or meeting specific compliance standards.

These necessities led us to develop two exciting features:

  • A unique cross-platform WinRM stack, which is the technology used by PowerShell to run scripts remotely;
  • Support for Devolutions Gateway.

By combining these two new features, you can now run an AnyIdentity provider script on a remote system through a Devolutions Gateway tunnel. Just imagine: you can securely manage PAM accounts —from anywhere in the world — tunneled through Devolutions Gateway with Devolutions Server and Remote Desktop Manager.

Running a PAM AnyIdentity provider over Devolutions Gateway

Thanks to PowerShell scripts, AnyIdentity providers now offer flexible Run as options, allowing you to run the AnyIdentity provider code nearly anywhere that it's needed.

  • Use the new WinRM stack as the default, or use the original “Legacy API” (potentially needed if running scripts locally on DVLS).
  • Specify a PowerShell configuration. The default is Microsoft.PowerShell, which runs in the older Windows PowerShell 5.1 environment. You can also specify a configuration like PowerShell.7, which runs in the recommended PowerShell 7 environment.
  • Choose to run the provider over a specific Devolutions Gateway instance.

Configuring a PAM AnyIdentity provider with Run as credentials
Configuring a PAM AnyIdentity provider with Run as credentials


Note: PowerShell 7 is not natively installed on most servers, and PowerShell remoting is not configured by default. We recommend installing PowerShell 7 and enabling remoting.

Devolutions Server for Linux (Beta)

You may have noticed that we recently introduced a beta version of Devolutions Server for Linux (Beta). With the previously mentioned options for AnyIdentity providers, you can run those scripts on a remote system without worrying about the Linux environment. Though PowerShell works on Linux, not all features and functionalities are available. With the option to run AnyIdentity in a remote environment through a Devolutions Gateway, you can run DVLS wherever you need it.

Run AnyIdentity providers anywhere

Ultimately, the flexibility afforded by the newest features introduced in Devolutions Server gives you what you need to run AnyIdentity providers anywhere. Whether you’re running DVLS on Linux (Beta) or Windows, you can manage your privileged accounts across your entire environment. Discover how these enhancements in Devolutions PAM help you take positive control of your privileged access environment today!

Related Posts

Read more Products posts