@arvind  - Have look at  /libs/dam/cfm/admin/clientlibs/v2/authoring/contenteditor/editors/StyledTextEditor.js

@Mhatri  Can you try- response.setContentType(ContentTypeUtil.TYPE_JSON); response.setCharacterEncoding(CharEncoding.UTF_8);

@Vainavee  - Sticky Session - 1-1 publish binding for subsequent request so session is sicky https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-to-do-configurations-for-sticky-session-in-dispatcher-and-in/m-p/281809 Permission Sensitive Caching - Delivering Secured Content...

@MM_AEM  -Check reference  https://experienceleaguecommunities.adobe.com/t5/adobe-experience-manager/how-can-i-access-the-user-login-details-in-publish/td-p/431960    

@Magicr - Refer https://blog.developer.adobe.com/aem-6-4-creating-a-scheduler-using-osgi-r6-annotations-4ad0b8c6fce7 Also @arunpatidar  is correct as per your code make sure you not missing configurations.  configurationPolicy = ConfigurationPolicy.REQUIRE   Thanks

@shabarish  - Any User/Group access restriction in publish should be based on CUG concept nothing to deals with everyone group. http://www.aemcq5tutorials.com/tutorials/implement-cug-aem/ https://experienceleague.adobe.com/docs/experience-manager-65/administering/security/cug.html?lang=en     Thanks...