Same ApiKey being used but after MG upgrade, even after giving valid apikey access_denied error is thrown.
what is the config that needs to be validated to address the issue?
MG v2.5.16 upgrade resulted in the access denied, eventhough no update has been made in the product or dev apps.
However the MG instance being switched to the new nodes.
User | Count |
---|---|
1 | |
1 | |
1 | |
1 | |
1 |