Enable and configure PowerShell script in Active Directory

Configure the Okta Active Directory agent to securely run a custom PowerShell script in your on-premises environment. Use this feature to execute custom lifecycle management (LCM) functionalities through PowerShell.

Before you begin

You've installed Okta AD agent version 3.23.0 or later.
A PowerShell script (.ps1) resides at an absolute file path on the AD server.
The script is signed on the device using a private key.
You have the corresponding public key or certificate. Okta accepts PEM-encoded RSA public keys, PEM-encoded public keys, and X.509 certificates (.crt or .cer).

Procedure

In the Admin Console, go to Directory > Directory Integrations.
Select your Active Directory instance.
Click the Provisioning tab, and then select PowerShell script in the Settings list.
Select Enable PowerShell script execution.
In PowerSchell script file path, enter the absolute path of the script.
Optional. Enter a Description for the script.
In Public key, click Add files to upload the public key or certificate.

Note: The public key field is write-only. After you save, the Admin Console doesn't display the key. Okta doesn't validate the key format when you save; invalid keys cause execution failures later.
Click Save.
Complete the authentication to verify your identity and save the configuration.

The script is configured and ready for invocation through Okta Workflows using the Okta public API.