ServiceNow Integration with ADManager

[miles9]

Hi, I did a quick search through the community and only saw one post on ServiceNow and ADManager but it was api and flow setup.  My issue is different.  I downloaded the ADManager plus integration from the store and already setup the ADManager plus side to connect with our non-prod instance.  The test connection was successful.

In ADManager plus we are able to generate an authtoken successfully.

In ServiceNow, when we click on Setup, we enter the ADManager URL and select our mid server.  This works fine.  The next screen when it asks for the ADManager Plus Technician Authtoken, we paste in the token we got from ADManager.  This is where we are stuck.  We receive an error message after clicking Validate "The given Authtoken is invalid." 

I have tested the "connection" by going to our mid server and I can pull up the ADManager URL and login fine.  

I have emailed manageengine support and am waiting for a reply.  Has anyone integrated ADManager with ServiceNow?  Would anyone be able to provide any insight as to what I can do to get past this third and final step?

Thank you

[Udayrathore049]

Checklist to Resolve the Invalid Authtoken Error

1. Ensure the Token is for the Right Technician

   • Go to ADManager Plus > Admin > Technicians

   • Confirm you're generating the token for a technician that has API access permissions and sufficient rights in ADManager.

2. Use the Correct API Authtoken Format

   • When generating the authtoken, do it from the same account you're using in ServiceNow.

   • Sometimes, copying the token from a different browser or session might lead to invisible characters—try regenerating it and pasting in a plain text editor first to clean it.

3. Check for Whitespace or Formatting Issues

   • Before pasting the token into ServiceNow, make sure there are no leading/trailing spaces.

   • Paste it into a Notepad or similar tool first, then copy-paste into ServiceNow.

4. Use a Static IP and Trusted Domain (Optional, but Sometimes Needed)

   • If you're running a tight firewall or proxy, you may need to allow the MID Server IP on ADManager's trusted list.

5. MID Server Permissions

   • Ensure your MID server has network access to ADManager and the proper Java version installed.

   • Also, make sure the MID server has HTTPS access if ADManager is using SSL.

[tinayang15]

Hi Miles,

We are running into the same issue - were you able to get this resolved?

[tinayang15]

Disregard, we reached out to ADManager Plus and they were able to find an issue which they gave us a patch and IAM team upgraded admanager plus application (NOT SN plugin - was already up to date).

[Ajay_Chavan]

@miles9

Quick Tests to Try

API Test: Use a tool like Postman or curl from your Mid Server to test the ADManager Plus API directly with your token
New Token: Generate a completely new authtoken with maximum permissions
Different User: Try creating a token with a different ADManager Plus technician account