dc
eeffa92f9e
makeDataServer.json seeded ADMIN=AllUsers, a Viya-style group that no account on the shared estate belongs to. The seed still reports SUCCESS with a group the caller is not in, and then every getdata/stagedata call aborts with '<user> is not authorised to edit <libds> in the MPE_SECURITY table', which reads like a broken deployment. The estate's accounts are in all-users, the SASjs Server group every logged-in user has, so seed with that and describe the rule in the estate-testing skill rather than telling the reader to override the shipped value.