Tagged: #OpenAM, Access Manager, oauth2, openidm This topic has 0 replies, 1 voice, and was last updated 2 years, 11 months ago by HicksRobertL. Author Posts October 15, 2019 at 6:03 pm #26866 HicksRobertLParticipant I am following the following guide: https://forum.forgerock.com/2018/05/forgerock-identity-platform-version-6-integrating-idm-ds/ Step #4 says to create the OAuth2 in the Top Level Realm: Select Top-Level Realm -> Configure OAuth Provider -> Configure OpenID Connect -> Create -> OK. We have set up a stateless realm for testing. Can I use the same steps but substitute our realm for the “Top-Level Realm” or does it have to be in that top-level realm? In the docs: https://backstage.forgerock.com/docs/am/6/oauth2-guide/#chap-oauth2-implementation It states “You must set up a standard policy in the Top Level Realm (/) to protect the authorization endpoint.” but in the example just after it shows: 1. In the AM console, select Realms > Realm Name > Dashboard > Configure OAuth Provider > Configure OAuth 2.0. 2. On the Configure OAuth 2.0 page, select the Realm for the authorization service. Which is confusing to me. — Robert Author Posts Viewing 1 post (of 1 total) You must be logged in to reply to this topic.