Difference between enabling/disabling and activating/deactivating a local user in AEM | Community
Skip to main content
A
aherbst
June 29, 2022
Solved

Difference between enabling/disabling and activating/deactivating a local user in AEM

  • June 29, 2022
  • 2 replies
  • 1905 views

When I go to Tools > Security > Users and select a user in AEM I see a list of actions that include Enable, Disable, Activate, and Deactivate but I don't know what these actions do

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 SantoshSai

Hi @aherbst ,

  • Activating/Deactivating 
    On publisher instance , it is not advisable to create any users/groups.
    If any user needs to login to publisher instance, we need to create or activate the user from author instance.If you activated the user/group from author, you can see the green box for that user/group. This means you have activated properly to publisher .
    Hence, you can login to publisher instance with same user name and password which activated from author instance.

    Deactivating takes place in reverse manner - which will remove use/group from publisher instance.

    When you Activate below property is set to user/group node



    When you Deactivate below property is set to user/group node



  • Enable/Disable
    If you wish user/group to have it remain on repo but want to get off all the access right - in that case disable will come into the picture so that you can simply enable/modify later instead creating it from scratch.

    When you Disable below property is set to user/group node

Hope that helps!
Regards,
Santosh

2 replies

ShaileshBassi
Community Advisor
ShaileshBassiCommunity Advisor
Community Advisor
June 29, 2022

@aherbst Sometimes, you might find yourself wanting to disable a user account in Adobe Experience Manager, while leaving the account itself intact. This is easy to do via curl:

curl -vfs -u admin:admin http://localhost:4502/.rw.html -F “disableUser=Disabled via curl”

This sets a protected property on the user node, called rep:disabled – as the term “protected property” suggests, you aren’t supposed to directly interact with that property, but rather it should be set through the appropriate service.

 

To later re-enable this user, just pass a blank value:

curl -vfs -u admin:admin http://localhost:4502/.rw.html -F “disableUser=”

This will delete the protected property, and re-enable the user.

 

This can be done using the GUI as well

 

 

Thanks

    SantoshSai
    Community Advisor
    SantoshSaiCommunity AdvisorAccepted solution
    Community Advisor
    June 29, 2022

    Hi @aherbst ,

    • Activating/Deactivating 
      On publisher instance , it is not advisable to create any users/groups.
      If any user needs to login to publisher instance, we need to create or activate the user from author instance.If you activated the user/group from author, you can see the green box for that user/group. This means you have activated properly to publisher .
      Hence, you can login to publisher instance with same user name and password which activated from author instance.

      Deactivating takes place in reverse manner - which will remove use/group from publisher instance.

      When you Activate below property is set to user/group node



      When you Deactivate below property is set to user/group node



    • Enable/Disable
      If you wish user/group to have it remain on repo but want to get off all the access right - in that case disable will come into the picture so that you can simply enable/modify later instead creating it from scratch.

      When you Disable below property is set to user/group node

    Hope that helps!
    Regards,
    Santosh

    Santosh Sai
      Terms & ConditionsAccessibility statement

      Loading footer...