Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AC Tool removes group association with custom group on AEM 6.5 #520

Open
hiralketanshah opened this issue Nov 25, 2020 · 3 comments
Open

Comments

@hiralketanshah
Copy link

hiralketanshah commented Nov 25, 2020

Hello,

We’re using Netcentric AC Tool release 2.5.3 to manage custom permissions in our AEM 6.5 project.
We recently ran into an issue where group association with custom group is getting removed automatically after the build.
Steps to reproduce :

  1. Add a group media-agency in the yaml file and let the AC tool create it in AEM.
  2. Now, create a new group test-group directly in AEM and associate it to the media-agency.
    image
    Now, deploy the code into AEM again, may be with no changes at all. Just a simple deployment.
    Exepected result : media-agency will still be associated to test-group.
    Actual result : media-agency is no longer associated to the test-group.

This isn't the same behaviour of group association with user. Group association with user will be persisted even after multiple deployments to the server.
Tried adding keepExistingMembershipsForGroupNamesRegEx: .* into the yaml file as well but didn't work as expected.

Any insights on how do I make it work for group associations? or is this a bug that needs to be addressed?

Thanks in advance.
Regards,
Hiral Shah

@kwin
Copy link
Member

kwin commented Nov 25, 2020

@hiralketanshah
Copy link
Author

@kwin Thanks for the link to the documentation.
Does that mean that adding the below code in yaml files would allow the custom AEM group to inherit from ACTool managed groups?

  • group_config:
    defaultUnmanagedExternalIsMemberOfRegex: .*
    defaultUnmanagedExternalMembersRegex: .*

If yes, I did try the same on my local, but didn't work. Also, this is not the case with Users. If an AEM user inherits from ACTool managed group, then it will persists the same always, after deployment as well.
Let me know if I am missing something.

@kwin
Copy link
Member

kwin commented Nov 25, 2020

Does that mean that adding the below code in yaml files would allow the custom AEM group to inherit from ACTool managed groups?
group_config:
defaultUnmanagedExternalIsMemberOfRegex: .*
defaultUnmanagedExternalMembersRegex: .*

defaultUnmanaged* is not supported within group_config but only within global_config (https://github.com/Netcentric/accesscontroltool/blob/develop/docs/AdvancedFeatures.md#configure-memberships-oftowards-externally-managed-groups)

Also, this is not the case with Users.

This is expected, citing from https://github.com/Netcentric/accesscontroltool/blob/develop/docs/AdvancedFeatures.md#configure-unmanaged-aspects

relationships to groups and system users are removed - relationships to regular users are untouched (those are often assigned by user administrators, LDAP or SSO)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants