cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Sync failed: Oauth problem advice: bad request (400)

Highlighted
New here

Sync failed: Oauth problem advice: bad request (400)

Have just taken over a Meraki environment that has passed through a few administrative hands.

I know that many of our networks' devices need to be re-enrolled because of noncompliant push certificate.

Is this error on attempted DEP sync related to that, or is it another issue entirely?

 

Been several years since I was a Meraki admin and could really use a bit of insight here.

 

1 REPLY 1
Highlighted
Meraki Employee

Re: Sync failed: Oauth problem advice: bad request (400)

Hello @docwindprod 

 

The DEP Sync failure could be due to the expired DEP Token or due to some issue on the Apple Servers while you were trying to Sync. But the re-enrollment due to non-compliant push Cert is due to an expired APNS Cert on the Meraki Dashboard. Both are two different issues. Please check the KBs I linked and let me know if you have any questions.

 

Regards,

Meraki Team

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.