GDPR is used as an example in the sections below, but the details covered are applicable to all data protection and privacy regulations; such as GDPR, CCPA etc.
At the AEM Foundation level, the Personal Data that is stored is the User Profile. Therefore, the information in this article primarily addresses how to access and delete user profiles, to address the GDPR Access and Delete requests respectively.
Open the User Administration console, by browsing to Settings - Security - Users or by browsing directly to https://<serveraddress>:<serverport>/libs/granite/security/content/useradmin.html
Then, search for the user in question by typing the name in the search bar at the top of the page:
Finally, open the user profile by clicking it, then check under the Details tab.
As mentioned, Adobe provides APIs for accessing user data, in order to facilitate automation. There are several types of APIs which you can use:
UserProperties API
curl -u user:password http://localhost:4502/libs/granite/security/search/profile.userproperties.json\?authId\=cavery
Sling API
Discovering the user home:
curl -g -u user:password 'http://localhost:4502/libs/granite/security/search/authorizables.json?query={"condition":[{"named":"cavery"}]}'
{"authorizables":[{"type":"user","authorizableId_xss":"cavery","authorizableId":"cavery","name_xss":"Carlene Avery","name":"Carlene Avery","home":"/home/users/we-retail/DSCP-athB1NYLBXvdTuN"}],"total":1}
Retrieving user data
Using the node path from the home property of the JSON payload returned from the above command:
curl -u user:password 'http://localhost:4502/home/users/we-retail/DSCP-athB1NYLBXvdTuN/profile.-1.json'
curl -u user:password 'http://localhost:4502/home/users/we-retail/DSCP-athB1NYLBXvdTuN/profiles.-1.json'
Open the User Administration console and search for the user in question, as described above.
Hover over the user and click the select icon. The profile will turn grey indicating that it is selected.
Press the Disable button in the upper menu to disable the user:
Fianlly, confirm the action:
The user interface will then indicate that the user has been deactivated by greying out and adding a lock to the profile card:
Log in to CRXDE Lite, then search for the userId
:
Open the user node which is located under /home/users
by default:
Delete profile nodes and all their children. There are two formats to the profile nodes, depeding on the AEM version:
/profile
/profiles
, for new profiles created using AEM 6.5.The following procedures use the curl
command line tool to illustrate how to disable the user with the cavery userId
and delete her profiles available at the default location.
curl -g -u user:password 'http://localhost:4502/libs/granite/security/search/authorizables.json?query={"condition":[{"named":"cavery"}]}'
{"authorizables":[{"type":"user","authorizableId_xss":"cavery","authorizableId":"cavery","name_xss":"Carlene Avery","name":"Carlene Avery","home":"/home/users/we-retail/DSCP-athB1NYLBXvdTuN"}],"total":1}
Using the node path from the home property of the JSON payload returned from the above command:
curl -X POST -u user:password -FdisableUser="describe the reasons for disabling this user (GDPR in this case)" 'http://localhost:4502/home/users/we-retail/DSCP-athB1NYLBXvdTuN.rw.userprops.html'
Using the node path from the home property of the JSON payload returned from the account discovery command and the known out of the box profile node locations:
curl -X POST -u user:password -H "Accept: application/json,**/**;q=0.9" -d ':operation=delete' 'http://localhost:4502/home/users/we-retail/DSCP-athB1NYLBXvdTuN/profile'
curl -X POST -u user:password -H "Accept: application/json,**/**;q=0.9" -d ':operation=delete' 'http://localhost:4502/home/users/we-retail/DSCP-athB1NYLBXvdTuN/profile'