- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Invalid API key Washington Servicenow
We are upgrading our SNOW to Washington version next month. When we test Meraki feed on latest plug in (1.4.0) we get the below error...
'Error in SG-Meraki Devices - Data Stream Action Splitter Step for Organization ID Method failed: (/api/v1/organizations//networks) with code: 401 - Invalid API key'
We know for sure the key is correct.. has anyone seen this and know how to fix?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would recommend running an API call in Postman, or something similar, using the same key to that same API end point and see what response you get
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have tried that and it confirmed the API key as valid.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would recommend reaching to Service Now support and Meraki support and maybe get both parties on a bridge call to troubleshoot this. From the Meraki point of view if the key is working in postman but not this application they are going to have you work with that applications support. Possibly grabbing the authorization header on the get call that service now is sending over.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for the suggestion - we are trying to organize this. From what we can see from the logs the endpoint is missing the customer account number.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Does Meraki have an logging on 401 errors or ability to troubleshoot them? They do not show in the Get Organization API requests call. Where would I need to instruct Meraki Support to look?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Are you looking for error logs in the ServiceNow plugin? you can navigate to Debugging > Error logs
some common reasons for 401 API errors in the plugin can happen if at least 1 org ID in the array of orgs you have passed is incorrect/does not have access. Try passing 1 org at a time to test this.
Also, try deleting the API key & pasting it again in the plugin and then run.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
No, this is not related to the ServiceNow plugin.
This question is specific to what abilities Meraki Support has to troubleshoot 401 errors.
Any help would be appreciated
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Don_Gruff , did yoy get the issue solved. Came across simislar error
orgStream: Method failed: (/api/v1/organizations) with code: 401 - Invalid API key
Data Stream Action Splitter Step Method failed: (/api/v1/organizations) with code: 401 - Invalid API key
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes it got resolved by upgrading the Meraki plugin on ServiceNow. We have a large number of plugins and accidentally overlooked this one when we upgraded.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Did you regenerate the API key after upgrading ?
Can you clarify if you had enabled the below
Organization settings - below 2 options asking for the IPs
Allow Dashboard and Dashboard API access to these IP ranges
Allow Dashboard API access to these IP ranges
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In our case we just needed to update the plugin and it worked without needing to do anything else
