Hey there,
So I’ve just tried locally with my user:
julian.gamble
//.. other json "acl": { "entries": [ { "claim": { "type": "http://epicgames.com/ue/horde/user", "value": "julian.gamble" }, "actions": [ "QueryMetrics" ] } ] }, //.. other jsonWithin the globals.json, and things eem to work just fine. I think it’s fundamentally the placement of the ACL information within the stores. If you move this back to the global level (and not within the plugins::analytics::stores scope) it should be OK. I’ll see if I can sort out why it’s not rolling up as it feels like this should* work.
Edit:
- After reading the code on the TelemetryController, I can see why this is the case
- We don’t look at the Store ACL Config for the views, as we currently just evaluate the global acl config first, authorize that level and then present the views.
I’ve added a ticket to revisit our ACL structure here to see if this makes sense, as analytics is still in experimental and we have room to modify this. In the interim, if you simply move the ACL configuration outside of stores within the global.json, you should be fine.
Julian