Integration Hub - Active Directory v2 Question

ServiceNowSteve
Giga Guru

‎10-05-2023 11:58 AM

Good Afternoon All,

 

I am having a real problem with getting a Flow Designer form to work in any way with the Active Directory v2 spoke for Integration Hub.

 

This is our very first attempt to use Integration Hub and here is what I've done so far:

 

  1. Made a "Connection & Credential Alias record (sys_alias) 
  2. Created a connection to the Alias record
  3. n the connection I set my host to our active directory domain controller and selected 'Use MID Server"
    ServiceNowSteve_1-1696531890138.png
    ServiceNowSteve_2-1696532028517.png

  4. In the credentials record that links to the connection record I added our mid server and put in our credentials and password which I know work because I can login to our mid server using those same credentials.ServiceNowSteve_3-1696532147908.png

    With all these parts I can use "Test Credentials" and if I point the test credentials to my MID server and authenticate it works but if I point it to my host server for AD it fails. 

    So what is going on? does my account need to be a domain admin or something to work across the different domains to do AD work? Am I missing something?

    I've tried to watch videos, read articles, etc.. to solve this problem but it seems like nobody has the exact same situation I do so the instructions are not clear enough to get me working. Any thoughts?
0 Helpfuls
  • 1,330 Views
2 REPLIES 2

jonsan09
Giga Sage
Giga Sage

‎10-09-2023 08:14 AM

Sounds like a permission issue, you can try verifying by running the powershell commands for AD spoke directly on your MID server logged in as the service account.

0 Helpfuls

Harini17
Tera Expert

‎08-16-2024 06:57 AM

We had the exact same problem and got into a call with ServiceNow. So for actions listed in the below KB article, yes you need admin access to the DC(Domain Controller). Our AD team is not  ready to give this access to the Service Account and so we have requested ServiceNow if an alternate solution exists. But haven't heard anything positive from them yet.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1005260

0 Helpfuls