How to set MID Server and Credential used for Orchestration Active Directory Activities

[Adarsh18]

Hi team,

I'm new to Orchestration and I was wondering where and how the MID Server and Credential are set for Orchestration Active Directory Activities. In IntegrationHub Microsoft AD Spoke, the credentials are set based on the connection/credential configured for the AD Spoke connection alias.

On using the 'Add User to Group' activity in Orchestration, I noticed the credential 'Windows MID Server Service Account'. being used for the activity.

Is there any way to manually set the connection/credential for the Orchestration Active Directory Activities?

Thanks in advance

[suvro]

Yes the conflict might be the issue as its may be selecting the wrong MID Server and using its service account. Changing the IP address might well resolve the issue

[Adarsh18]

Sorry for replying late. Yes, the issue does seem to be the AD Activity choosing the wrong MID Server (due to same ip address) during runtime.

Aside from changing ip or removing the other MID Server, is it possible to force Orchestration to use the the MID Server and Credential I need or any other alternatives?

Thanks

[suvro]

As far as I understand, it uses a powershell script in the background to add user to a group. If you can modify that powershell script to use hard-coded username password

Or if you can modify the activity to add inputs of username and password and modify the background powershell activity to receive inputs for username and password and use the same.

As I am not a powershell expert so cannot help with the powershell script. You can get in touch with some windows admin for help

[Adarsh18 · Accepted solution]

Sorry for getting back late. I raised a ServiceNow support ticket on this and they confirmed that we cannot manually specify the MID Server for the AD Orchestration activity like we can do in IntegrationHub AD Spoke.