AEM 6.5 Tracking configuration changes | Community
Skip to main content
M
MukeshAEM
Level 3
January 3, 2023
Solved

AEM 6.5 Tracking configuration changes

  • January 3, 2023
  • 1 reply
  • 759 views

Hi Everyone,

 

I'm struggling to find the best way to manage and track any configuration changes done using config manager http://localhost:4502/system/console/configMgr. It's hard to track the changes done by someone with a team having a large number of team members with Admin rights on the AEM instance. I can see the configuration files available at path <Install Path>\crx-quickstart\launchpad\config\ but wondering if there is a way to check who made the changes.

 

Wondering if anyone can suggest the best practice to track the changes in configurations.

 

Thanks.

Mukesh 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by nitesh_kumar-1

Hi @mukeshaem ,

 

You can check access.log and error.log

 

However In this case, the best practice would be:-

1.) To limit the "admin" permission to the user who actually needs it, too many people should not have these permissions, especially in the upper environments.

2.) Create a group whose members are to be granted access to Web Console instead of allowing access to individual users, you can add these groups to "Apache Sling Web Console Security Provider" in the configuration.

3.) Make sure the OSGi configurations are only deployed with code that is committed in the source control (this is more future-proof if you are planning to move to the cloud in the future) and also provide proper tracking of the changes.

 

Hope this helps.

 

Regards,

Nitesh

1 reply

nitesh_kumar-1
Adobe Employee
nitesh_kumar-1Adobe EmployeeAccepted solution
Adobe Employee
January 3, 2023

Hi @mukeshaem ,

 

You can check access.log and error.log

 

However In this case, the best practice would be:-

1.) To limit the "admin" permission to the user who actually needs it, too many people should not have these permissions, especially in the upper environments.

2.) Create a group whose members are to be granted access to Web Console instead of allowing access to individual users, you can add these groups to "Apache Sling Web Console Security Provider" in the configuration.

3.) Make sure the OSGi configurations are only deployed with code that is committed in the source control (this is more future-proof if you are planning to move to the cloud in the future) and also provide proper tracking of the changes.

 

Hope this helps.

 

Regards,

Nitesh

    Terms & ConditionsAccessibility statement

    Loading footer...