@SaiM - You need to bind the selected value on dialog-ready event. Inside your javascript you will have to do something like this (you may have to update it if this is inside a multi-field). (function(document, $) { "use strict"; $(document).on("dialog-ready", function () { $("coral...

@SaiM - It looks like a case when your field value is not getting stored at all. Or it could be getting stored at a different node/path. Can you check in crx/de when you author it?If you still feel the issue is there, maybe share the dialog xml and we can see what could be the issue.thanks.

@Sandeep_Danny95 - I don't think it should be an issue with AEMaaCS or 6.5.I have uploaded a new asset with "Admin" user. Then I login as my test user.For this user, it has all rights but deny for 'dc:title' and 'dam:status' only.Therefore, I am able to edit the description with this. If I try to up...

@Sandeep_Danny95 - You can also validate if these ACLs are being applied for your user. in CRXde lite - http://localhost:4502/crx/de/index.jsp Go to this path (assuming default workspace) - /jcr:system/rep:permissionStore/crx.default    

@Sandeep_Danny95 - I have executed this on my local AEM 6.5 (SP23) instance and it works fine. 'user-kamal-kishor' is a user with 'Authors' and 'Contributors' group. set ACL for user-kamal-kishor allow jcr:all on /content/dam restriction(rep:glob,/test) deny jcr:modifyProperties on /content/dam re...

@Sandeep_Danny95 - I believe you have shared partial script here. Can you try this way please - set ACL on /content/dam //other statements... deny jcr:modifyProperties for user2 restriction(rep:itemNames,prop1,prop2) end  Reference: https://sling.apache.org/documentation/bundles/repository-i...

@arunpatidar - Thanks Arun. We have similar logic, additionally we are checking with session as well. This is referenced from adobe documentation - https://experienceleague.adobe.com/en/docs/experience-manager-dispatcher/using/configuring/permissions-cache#example-servlet   This statement takes bit ...

@giuseppebaglio  - thanks for your response. We are already filtering the requests to bare minimum. We have use-cases where some set of pages would be requested about 10k times in span of few minutes. These are all legitimate requests and need permission check before being served from cache. For tha...

@Srinath_A  - Thanks for your response.We have pages which may have CUGs applied to them and we have multiple sites (100s at-least) and there could be different scenarios with CUGs applied to them.I don't see the approach you have suggested to work very well for us.    thanks.

We are using session based check to determine if a request should have access to a resource. This is causing massive performance hit on our instance when the load becomes slightly higher (it is relative as we have many sites hosted and have adequate infra for on-prem instance).We are referring - htt...