@Jörg_Hoh  Are you referring Apache Sling Job Thread Pool OSGi configuration here? Please correct me.  

I believe you have noticed that error message in error.log file. If yes, then please check whether you are seeing any query like the below one in error.log file - query=select [jcr:path], [jcr:score], * from [dam:Asset] as a where [jcr:content/contentFragment] = 'true' and [jcr:content/data/cq:model...

rep:authorizableId The id that you would lookup the user in the authorisation api rep:principalName The principal nameShould be the same as the authorizableId   Please refer https://blogs.taylor-made-software.co.uk/aem/101/build/apps/users.html and Solved: Re: com.adobe.granite.security.user.UserPr...

If you want to restrict the access to content on an AEM publish instance[Grants read access to a set of users/groups. Denies read access to all other users/groups.] then use Closed User Group.   Could you please brief us about the requirement.

Understood. You are trying it on AEM publish instance, right?   if I do the same thing on AEM publish instance then I am getting similar ACL under permission tab like you -     I have noticed this ACL level difference between AEM author and publish instance associated with everyone user group.  

I have tried same thing on AEM6.5.9 as shown below -     Below is the ACL -   Could you please check the Groups tab whether that user is a member of any other group or not -      

Are you planning to do it permanently?    As @arunpatidar has mentioned if we stop the Scheduler via http://localhost:4502/system/console/components  then the relevant job will be removed from /system/console/status-slingscheduler (tested on my local AEM instance). But once you redeploy your bundle ...

I can't use both coral2 and coral3 in same component. Most of the project specific components are using coral2. Now I have decided to use /libs/granite/ui/components/foundation/form/userpicker.   Here is my node structure details -   Approver page property details has been shown below -        

Hi @arunpatidar ,   I saw your blog already and sure I will give a try with this. Though we are using AEM 6.5.x, but still components are using Coral2. I can say this much only about the use case.   Initially I wanted to create an autocomplete page property with /libs/granite/ui/components/coral/fou...

I have created one page property named: Content Approver Group with sling:resourceType: granite/ui/components/coral/foundation/authorizable/autocomplete   This autocomplete page property named: Content Approver Group is designed to allow the content authors to pick the user group from suggested list...