User group "Everyone" has its permissions reset after server restart

[SHIBANI06]

Is it possible to retain "everyone" group permission after server restart? so that admin user does not have to login and set permissions manually for this group?

[SreenivasBr · Accepted solution]

It is not recommended to modify the permissions for everyone group. Refer - https://experienceleague.adobe.com/en/docs/experience-manager-65/content/security/security?lang=en#b...

If you want everyone in the team to have certain permissions, it is recommended to create a custom user group and then assign everyone to that group.

[AmitVishwakarma]

Yes, it is possible to retain the "Everyone" group permissions after a server restart in AEM. The issue you're experiencing might be due to temporary configurations or repository inconsistencies. Here's how you can address this:

Solutions to Retain "Everyone" Group Permissions:

1. Check Replication and Persistence Settings: Ensure that the permissions are being persisted correctly in the repository and not being overwritten by the dispatcher or replication process. Sometimes, if there is an issue with replication or crx persistence, changes might not be saved correctly.

2. Ensure Consistent Group and Permissions Configuration:

   • Make sure that permissions for the "Everyone" group are correctly set at the JCR level.
   • Verify that the permissions are stored in a persistent configuration (not cached) in the AEM repository (/home/groups/everyone).

3. Backup and Restore Permissions:

   • You can manually back up the permissions configuration (for example, using CRX or a tool like CRX Package Manager).
   • After the server restart, restore the configuration using import/export functionality to apply the saved settings for the "Everyone" group.

4. Use AEM System User: You can create a system user or script to automatically reapply the permissions upon restart using AEM workflow or startup scripts that run after server startup.

5. Check for Custom Scripts or Filters: If you have any custom scripts or filters in place, ensure that they aren't resetting the permissions upon server restart. This can happen if the server is being reset to default configurations.

Summary:

To retain the "Everyone" group permissions after a restart, ensure that permissions are correctly saved in the repository, not overwritten by replication, and consider using backup/restore methods or custom scripts to reapply permissions automatically.

[kautuk_sahni]

@SHIBANI06 Did you find the suggestions helpful? Please let us know if you require more information. Otherwise, please mark the answer as correct for posterity. If you've discovered a solution yourself, we would appreciate it if you could share it with the community. Thank you!