Hi
We are following Oauth2.o approach access protected files from client (non-AEM) by defining custom scope where we have provided read only access to folders/files.
Use Case:
.
Above use case is working fine in AEM author where we are getting authorization code and receiving access token by making call from postman and able to get protected file information.
We are facing some challenges to implement this in the publishing domain. Please let me know if input on below issue.
How do we bypass access confirmation step in AEM dispatcher path as there is no option to login & authorized access while generating authorization code?
Can we bypass the access confirmation step while generating authorization code as it requires manual login and authorization.
We enabled OAuth Server Authentication Handler on Publisher domain and configured below rules in dispatcher filter but /oauth/authorize & /oauth/token are not working with domain URL.
/0217 { /type "allow" /method "GET" /url "/oauth/authorize" }
/0218 { /type "allow" /method "POST" /url "/oauth/token" }
Solved! Go to Solution.
This feature is not supported for publish and in near future also there is no road map for this.
Hi Nishant,
I am following same approach and its work fine in author environment.
When I am trying to implement same in Publish domain, below request looking for user login option to authorize request but in publish domain we don't have login option to authorize and generate code.
This feature is not supported for publish and in near future also there is no road map for this.
Views
Likes
Replies
Views
Likes
Replies