Service Graph connector app for ServiceNow error - API KEy

[arielgritti]

Hi community,

We're trying to configure the Service Graph connector app for ServiceNow.

Our Meraki admin has created the API KEY.

We've created credentials (using the API KEY) and connections.

When we try to test the data source import, an error is raised:

Error in MerakiGetOrganization - orgStream: API Key missing access to organizations: 999999 (it's a fake number, here is our Organization ID; we're using initially only 1 organization).

Our Meraki admin told me the API KEY have at least read access to this organization.

Any idea?

I've created a ServiceNow case too.

Thanks,

Ariel

[alemabrahao]

Hi, check this article.

https://developer.cisco.com/meraki/build/servicenowsupport/#unable-to-receive-alert

[arielgritti]

Hi @alemabrahao 

I'll take a look and back with you.

Thanks,

Ariel

[GreenMan]

Have you tried using the same API key to make some basic calls using something simple like Postman?

[arielgritti]

Hi @GreenMan 

I was thinking about it just a few minutes ago.

Let me try to validate if the API Key is working fine.

Thanks,

Ariel

[arielgritti]

Hi @GreenMan 

Finally, it worked from Postman.

Reading Meraki API documentation, I found this: The name to use is: "X-Cisco-Meraki-API-Key" in the Authorization for the API KEY value, and the URL is: https://api.meraki.com/api/v1/

[GreenMan]

Also:    does ServiceNow integration maybe require something beyond read-only permissions?

[arielgritti]

I'm following (really our Meraki admin is following) this doc from Cisco Meraki app published in the ServiceNow store: https://developer.cisco.com/meraki/build/servicenowservice-graph-connector-for-meraki/

Here you can see this:

And this

I don't have admin access to Meraki Dashboard. I can't validate how the API KEY was created and what role or permissions it has. I'm asking our Meraki admin.

Following the document, I saw this: https://developer.cisco.com/meraki/api-v1/get-organizations/ to do a test.

In our configuration we have: https://api.meraki.com/api/v1 I believe we have a typo there. I changed to https://api.meraki.com/api-v1 and I'm retesting it.

[arielgritti]

Using the API KEY in Postman 

Status 200 OK

And I have that answer for https://api.meraki.com/api-v1/get-organizations

[arielgritti]

The Meraki doc is saying to use this URL: https://api.meraki.com/api/v1

[arielgritti · Accepted solution]

Hi all,

Finally, the issue was the whitelist in the Meraki dashboard. We wrongly whitelisted "inbound" ServiceNow IPs instead of whitelisting "outbound" ServiceNow IP range. Doing that, the Service Graph Connector for Meraki has started working fine.

Thanks @shwetaP for your help to fix it pointing us in the right direction.