-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Meraki Rest API information is out of date and failing to connect #11248
Comments
Hi @giveen, Thanks for flagging this issue, we will investigate this issue and get back to you with some updates. Thanks! |
Hi @giveen, Could you please share the screenshot of the error message when you're getting after clicking on connect. Thanks! |
Hi @giveen, After analysis of existing code, we made changes into the REST API authorization and making it to get updated as per Cisco Doc. The PR has been raised with changes and currently it is in review state.
The custom deployment steps are mentioned into below file : Many Thanks! |
Wow you guys are faster than me. I'll test the deployment you sent me and get back to you guys, but here is the rest of the details requested. Here was my test script
Returned:
Considering the new API, this was my script
Result:
|
|
Hey @giveen, Today I have check with above scripts Old and New one to check the response for the Org Name and Org Id, and received the successfully response for both of them, there no issue currently having with the old API. And from our end we can be able to connect the existing connector without any fail: Let's check with your credentials to our updated connector, I see your getting the deployment error is may due to while deployment of template you did not enter the correct values, so please add below values and re-deploy the template - |
I was able to deploy the template with no issues after adding in my Workspace-location, and Workspace name. However, after putting in my Org ID and API key from the Data Connectors page, same result of 404. |
If you look at my test script, you will see that Org-ID is no longer needed. When just inputting my API key, Cisco new which Org I belonged too. |
Hi @giveen, Thanks for your response. Did you check the same for cisco end for 404 error? if any permissions or settings required and it should be disable currently? |
Good morning, I will email you from my work email and will reference this . |
Hi @giveen, I see your mail, in that the Workspace ID and sub key has been shared, actually to access it from backend we don't have required permission. Thanks! |
I have confirmed the org id matches my records and go ahead and send me a teams invite. |
Describe the bug
The Meraki Rest API is using an out of date authorization behavior
https:/Azure/Azure-Sentinel/tree/master/Solutions/Cisco%20Meraki%20Events%20via%20REST%20API/Data%20Connectors
https://developer.cisco.com/meraki/api-v1/authorization/#obtaining-your-meraki-api-key
"Next, check that your API call has the correct header with the following (and not v0's X-Cisco-Meraki-API-Key):"
https:/Azure/Azure-Sentinel/blob/master/Solutions/Cisco%20Meraki%20Events%20via%20REST%20API/Data%20Connectors/CiscoMerakiMultiRule_ccp/dataConnectorPoller.json
Line 17
"ApiKeyName": "X-Cisco-Meraki-API-Key"
The text was updated successfully, but these errors were encountered: