FAQ 5: Delete a merchant

Script to disable a merchant. This script depends on disable-user.groovy so make sure they live in the same directory. Both scripts are also found on github in saas/system/scripts.

Must provide:

ah : the API Host - for example, dev would be http://tsa-chef-qa1:8080/sapi/rest/
uuid : the uuid of the merchant OR e : the email

To run:

groovy disable-merchant.groovy -uuid merchantUUID -ah URLtoYourAPIHost
OR
groovy disable-merchant.groovy -e merchantEmail -ah URLtoYourAPIHost

12/13: Fixed! The default merchant user uses their token to deactivate the entire merchant group (including themself). First the merchant user deactivates the merchant group with their token, then all group members are deactivated with the TSA token. Elastic search is not updated when each user is deactivated (because the TSA Admin token is used) so we may run into/have to work around issues in the future if we rely on elastic search for user retrieval (with a call to get or to search).

12/11: Default merchant user and all users in the group are disabled when the script is called. However, there is still an outstanding bug/security issue in the system where I am unable to properly update the elastic search index. Because merchant retrieval depends on elastic search, AML-941 is directly affected.

12/10: Due to a bug in the system, the default merchant user is not disabled with this script. If it needs to be done, disable-user.groovy can be called with the default merchant user's id. In addition, no other members of the merchant group are disabled.