Getting 403 error while trying to access Client Libra...

[a_mn1]

Hi All,

I have my AEM 6.5 Assets instance integrated with Siteminder for SSO login.  My login is successful . However I am not able to see few pages. Especially the content fragment model creation page. Upon my investigation found out that the client libraries under the /libs folder are not getting loaded.  the access logs shown 403 error. 

I checked the users access, in AEM and he has all relevant access. I could see the requests for all css or js under /libs are coming with anonymous user instead of the actual logged in user in the request.log. 

 But for such request , the SSOAuthentication handler is printing the users employee ID.

Below is the extract from my access log. The requests under /libs is coming as anonymous

<server ip> - <my emp id> 23/Jan/2020:12:49:58 +0530 "GET /mnt/overlay/dam/cfm/models/editor/content/editor.html/conf/store/settings/dam/cfm/models/blog-creation-model HTTP/1.1" 200 58427 "https://xyz.myhost.net/libs/dam/cfm/models/console/content/models.html/conf/store" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36"
<server ip> - anonymous 23/Jan/2020:12:49:59 +0530 "GET /libs/dam/cfm/models/editor/components/formbuilder/clientlibs.css HTTP/1.1" 200 1962 "https://xyz.myhost.net/mnt/overlay/dam/cfm/models/editor/content/editor.html/conf/store/settings/dam/cfm/models/blog-creation-model" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36"
<server ip> - anonymous 23/Jan/2020:12:49:59 +0530 "GET /libs/dam/cfm/models/editor/components/formbuilder/clientlibs.js HTTP/1.1" 200 37696 "https://xyz.myhost.net/mnt/overlay/dam/cfm/models/editor/content/editor.html/conf/store/settings/dam/cfm/models/blog-creation-model" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/79.0.3945.117 Safari/537.36"

So I am bit confused what could be causing this issue. Any help on this is appreciated,

[arunpatidar · Accepted solution]

Is author instance behind dispatcher? If yes then check dispatcher rules.
Try with admin credentials as well to narrow down permission related issues.