topic Re: Invalid API key Washington Servicenow in Network Platform API

Invalid API key Washington Servicenow

Don_Gruff — Mon, 20 May 2024 11:45:55 GMT

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?

Re: Invalid API key Washington Servicenow

AMP2 — Mon, 20 May 2024 16:17:06 GMT

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

Re: Invalid API key Washington Servicenow

Don_Gruff — Mon, 20 May 2024 16:19:56 GMT

We have tried that and it confirmed the API key as valid.

Re: Invalid API key Washington Servicenow

AMP2 — Mon, 20 May 2024 16:24:34 GMT

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.

Re: Invalid API key Washington Servicenow

Don_Gruff — Thu, 23 May 2024 08:43:23 GMT

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.

Re: Invalid API key Washington Servicenow

ServiceNow_User — Fri, 25 Oct 2024 10:29:08 GMT

@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

Re: Invalid API key Washington Servicenow

Don_Gruff — Fri, 25 Oct 2024 10:31:39 GMT

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.

Re: Invalid API key Washington Servicenow

ServiceNow_User — Fri, 25 Oct 2024 10:34:46 GMT

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

Re: Invalid API key Washington Servicenow

Don_Gruff — Fri, 25 Oct 2024 10:43:26 GMT

In our case we just needed to update the plugin and it worked without needing to do anything else

Re: Invalid API key Washington Servicenow

Andy Mikulas — Fri, 01 Nov 2024 13:07:40 GMT

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.

Re: Invalid API key Washington Servicenow

shwpalan — Wed, 06 Nov 2024 01:21:31 GMT

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.

Re: Invalid API key Washington Servicenow

Andy Mikulas — Wed, 06 Nov 2024 13:03:07 GMT

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.