Meraki API - TLS Cert validation issues

[gyro1]

We have been using the Meraki MP API (Mega proxy?) for a while now, to pull in Meraki events into Splunk. It works great, up until about a week ago when it all stopped suddenly. Digging into it, it looks like the TLS certificate was updated for https://api-mp.meraki.com/, but since 'api-mp' is not listed in the cert's common name or alt names, validation fails. You can see the issue by browsing to https://api-mp.meraki.com/ with Chrome.

I've tried searching around for any evidence the MP API was deprecated or changed, but didn't find anything. Has anyone else seen this issue, found a solution, or raised with Cisco? Seems like someone stuffed up the certificate renewal, and missed a hostname..

[Rasmus Hoffmann Birkelund · Accepted solution]

The mega proxy is being deprecated, so you should use api.meraki.com instead.

[Rasmus Hoffmann Birkelund]

I'm not sure if this is available for public, but for reference; https://community.meraki.com/t5/Developer-Early-Access/api-mp-meraki-com-is-now-deprecated-please-use-api-meraki-com/ba-p/116260

[gyro1]

Unfortunately that page is not publicly available, but knowing the MP API is indeed being deprecated is very helpful, thanks!

[Kenneth_rf]

I have the same problem. Anyone know if there is a solution?