@Jai1122-1) if you are creating the JCR Session in your code (ie. calling repository.login(..)) then you are responsible for closing that JCR Session (preferably in a finally block). Your JCR Session used to create a cq:User and/or its Token has nothing to do with the security context the user gets ...

Yes, but only if you create that new JCR session/resourceResolver (aka get a service user resourceresolver) you should close it as quickly as possible, ie. when you're done with it. Don't leave them hanging around for any longer than you need them. As Ideally you re-use the resource resolver from wi...

Hi, Unfortunately, this looks like a regression. Please log an issue with Adobe Support so AEM Engineering team can resolve. You could look at injecting some CSS that resolves this issue in the interim. 1. Make a new cq:ClientLibraryFolder under /apps to hold your temp fix. Assign this ClientLibrary...

100% don't initialize a resource resolver in your activate method. Keep your ResourceResolvers/JCR Sessions short-lived as you can. Also, rememeber resourceResolvers and JCR Sessions are NOT thread-safe. So if you had a servlet being hit by 2 ppl at the same time, and they both invoke the RepoUtil s...

I think youll need to investigate more. Does this happen on your local dev? Does this happen if you hit your custom servlet directly on AEM (vs. going through dispatcher)? What is the Request Progress log for this request (available in OSGi console)? Does your custom servlet have any code that could...

Deleted response. See response in comment below.

I assume by "sonar properties" you mean setting blanket exclusions at the POM level? It's typically unwise to blanket exclude entire packages/classes from code quality checks. What you should  do is:1. Review violations reported by Cloud Manager, and fix the ones you can1. There may be reported issu...

Can you please add more details to this? Which POST requests exactly? What servlets are you hitting? What's going in the error.log?

Do you have anything in your <PROJECT>>/core/target/classes/OSGI-INF folder? You should have a number of XML files, and a metatype folder with more XMLs. Does this exist?

Another interesting solution could be the following: 1. For each role/path combo - create a  Hidden predicate on the Assets Search Form 1. Use the excludespaths QueryBuilder predicate to exclude a specific path/path-pattern -- test this out as excludepaths seems like it might be a little slower, you...