Expand my Community achievements bar.

Dive into Adobe Summit 2024! Explore curated list of AEM sessions & labs, register, connect with experts, ask questions, engage, and share insights. Don't miss the excitement.

Where is Adobe Granite OAuth Resource Server in AEM 6.2?

Avatar

Level 2

I am trying to implement OAuth functionality in AEM 6.2 (based on this Presentation: https://docs.adobe.com/ddc/en/gems/oauth-server-functionality-in-aem---embrace-federation-and-unlea....).

I was able to make this work in AEM 6.1 since I can find the Service configuration of "Adobe Granite OAuth Resource Server" it's in the Web Console (http://localhost:4502/system/console/configMgr). But it's not there in AEM 6.2. Can someone point me, how to modify the allowed scopes in 6.2?

Also, has anyone implemented OAuth in there servers like this? If not, what was your approach?

3 Replies

Avatar

Level 9

I don't know, but perhaps it was renamed to this ...?

Adobe Granite OAuth Server Authentication Handler (see attached screenshot)

- JK

Avatar

Level 2

Hmmm, i don't think so. 'Adobe Granite OAuth Server Authentication Handler' exists both in 6.1 and 6.2. Also it doesn't have the 'Allowed Scopes' option. frown

Avatar

Level 2

Hi,

Did anyone resolve how to set the scope in 6.2?

I've been resolving issues via: http://help-forums.adobe.com/content/adobeforums/en/experience-manager-forum/adobe-experience-manage...

BUT this discussion matches my current issue which is:

Next step is to change scope from 'profile' to '/content/dam' in order to fetch content. This gives me an error 'invalid_scope', which makes sense as the OAuth Client is not configured to allow this scope yet. Trying to configure it and on /system/console/configMgr I see no 'OAuth Resource Server' configurations. Also, if I browse to /system/console/configMgr/com.adobe.granite.oauth.server.impl.OAuth2ResourceServerImpl I will get this error message:

        
    

This form is automatically generated from existing properties because no property descriptors are available for this configuration. This may be cause by the absence of the OSGi Metatype Service or the absence of a MetaType descriptor for this configuration.

  

Does it mean that our installation is missing a module required for OAuth?

Thanks.

 

Mike