Workflow action "Windows Server" execute powershell

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi Everyone,

Has anyone used “Windows Server” action in workflows? It can successfully connect to the server and execute a PowerShell script. The script correctly receives parameters passed from the workflow. However, when attempting to run Active Directory commands like Get-ADUser or Set-ADUser, it fails with the following error:

“Unable to contact the server. This may be because the server does not exist, is currently down, or does not have Active Directory Web Services running.”

Has anyone encountered this issue or have insights into resolving it?

2

@colin_mckibben could you please assist here

3

Can you try to put on the powershell some type of logs? it will be helpfull if you are trying to run it with enough permissions

Regards,

Pablo

4

Hi @pablonovoa,

The error shared above is from the logs itself. The AD commands are enclosed within a try-catch block, which captures the error and logs it accordingly.

To add, the windows server action is using iqservice server and iqservice user and password which has all permissions to perform provisioning from SailPoint

5

Hi Priya Rudra,
We had the same error and solved it by using Kerberos authentication because NTLM did not support the credential delegation required by Active Directory cmdlets when run through the PTA’s remote PowerShell session. Also check that the user is the AD samaccountname with nothing in front of it (parameter storage).
Best regards,

Miguel

1 Like