API server error when authorizing

Hello, some changes were made to how permissions were handled around REST in v12. You can see all of the changes here in our release notes: https://community.telligent.com/community/12/a/user-documentation/UD382/release-notes-for-community-12

This part in particular piece may be what you need to review: 

• REST API Key Access
  • What changed?
    • Accessing REST using an API key is now authorized using the 'REST API Key Access' permission.
  • What do I need to do?
    • Any users that you want to allow accessing REST via API key must be put into the upgraded role 'API Access By Key' or the 'REST API Key Access' permission must be added to any new or existing roles that require this level of access.‘’

Review your permissions and ensure you have this one in the Admin panel. I’ll ask if anyone else has suggestions to please chime in as well. Thanks!

Hey Grant,

Thank you for your response.  We found the role and applied it to the admin account as well as my user account, but it did not resolve the error.  Anything else I should try?

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?

Also note the API key role mentioned is not going to apply to OAuth

Hey Patrick,

Regenerating the secret fixed the issue.  Not sure why it was needed, but it got me back up and running.  Thank you!

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