API server error when authorizing

We just migrated to 12.1 and I am no longer able to authorize and receive an access token. Instead I receive a server error like so. I am using PostMan. Again, this was working before the migration. What does this mean and what should be done to fix this?

Top Replies

Patrick M. over 2 years ago in reply to sshaw9 +1 verified

Migrated or upgraded and from what? Did you try regenerating your secret and ensure that both the client id and secret are url encoded? Did you review the exception log?

Parents

0 Former Member over 2 years ago

The client application gets an HTTP status code of 500 with the message "Internal Server Error" as a response for API calls. The 500 Internal Server error could be caused by an error during the execution of any policy within Edge or by an error on the target/backend server.

The HTTP status code 500 is a generic error response. It means that the server encountered an unexpected condition that prevented it from fulfilling the request. This error is usually returned by the server when no other error code is suitable.

Greeting,

Rachel Gomez
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Former Member over 2 years ago

The client application gets an HTTP status code of 500 with the message "Internal Server Error" as a response for API calls. The 500 Internal Server error could be caused by an error during the execution of any policy within Edge or by an error on the target/backend server.

The HTTP status code 500 is a generic error response. It means that the server encountered an unexpected condition that prevented it from fulfilling the request. This error is usually returned by the server when no other error code is suitable.

Greeting,

Rachel Gomez
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data