Upgrade from 1.62.0 to 1.69.2 fails to authorize /oauth2/token requests with a 400
-
We have two development instances of Cloud FusionAuth (dev and staging).
We upgraded and tested in dev from 1.62.0 to 1.69.2.
After upgrade in staging from 1.62.0 to 1.69.2, users cannot login using SSO. I cannot determine why the staging instance is failing the SSO login process, when the dev instance continues to work.
It appears our call to https://{instanceName}/oauth2/token with {client_id, client_secret, code, grant_type, and redirec_uri} returns a 400 bad request error.
I cannot identify the difference between the two instances. -
@chatteberg I just saw your post. If you have a paid support plan you can open a ticket. If you do not have a paid support plan, are you still experiencing the issue?
