Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Identity Management (MOSC)

OAM through error whenever Scope parameter is added to oAuth Request

Mar 4, 2019 2:11PM edited Mar 12, 2019 5:00AM in Identity Management (MOSC) 2 commentsAnswered

Every time we add a scope parameter to the oAuth API token endpoint to get an access token, the server return 500 error.

If we take out the scope parameter it works fine.

Tagged:

Access Management

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month