Meraki API - TLS Cert validation issues

SOLVED
gyro
Conversationalist

Meraki API - TLS Cert validation issues

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..

1 ACCEPTED SOLUTION

Accepted Solutions
rbnielsen
Head in the Cloud

Re: Meraki API - TLS Cert validation issues

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

 

 

View solution in original post

4 REPLIES 4
rbnielsen
Head in the Cloud

Re: Meraki API - TLS Cert validation issues

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

 

 

View solution in original post

rbnielsen
Head in the Cloud

Re: Meraki API - TLS Cert validation issues

gyro
Conversationalist

Re: Meraki API - TLS Cert validation issues

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

Kenneth_rf
Here to help

Re: Meraki API - TLS Cert validation issues

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

Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.