Page MenuHomePhabricator

Grant Access to PII in Superset for samwilson
Closed, ResolvedPublic

Description

  • The username of your existing account on wikitech.wikimedia.org: samwilson
  • Do you currently have shell access (Yes/No)? Yes
  • Purpose (Specify which service you need to get access to, e.g. Icinga, Grafana, Superset etc): Superset
  • The specific LDAP group that you want to be added to (optional):

Superset access required for CommTech's work with Realtime-Preview-Wish-2021, can be revoked after that project is complete (~3 months from now).

Event Timeline

Noting https://ldap.toolforge.org/user/samwilson is already in the wmf group, so @Samwilson should be able to get past the login screen at superset.wikimedia.org and view some dashboards (that do not access private data).

Hey there @MMandere and @Urbanecm, he needs access to private data as well.

Sorry! I totally meant to add that. Thanks.

Samwilson renamed this task from Grant Access to Superset for samwilson to Grant Access to PII in Superset for samwilson.Nov 22 2021, 11:18 PM

Change 740826 had a related patch set uploaded (by MMandere; author: MMandere):

[operations/puppet@production] admin: Add samwilson to analytic privatedata group

https://gerrit.wikimedia.org/r/740826

Change 740826 merged by MMandere:

[operations/puppet@production] admin: Add samwilson to analytic privatedata group

https://gerrit.wikimedia.org/r/740826

MMandere claimed this task.

@Samwilson you now should be able to access the private data. Please let us know if you face any challenges.

Thanks!

I'm still getting an error when I try to view FROM event.visualeditorfeatureuse:

Permission denied: user=samwilson, access=EXECUTE, inode="/wmf/data/event":analytics:analytics-privatedata-users …

I've tried logging out and in again but still get it. Does the permission change take some time to sync?

@Samwilson, checking I'll advise once done.

@MMandere don't worry, it's working now! :-) thanks!

@Samwilson Great, you're welcome! Is there something else you did for it to start working?

No, I don't think so. I did try logging out and in again, but the fix came some time after that.

@Samwilson : It seems related to Puppet (our configuration management system) run times. Your update that it was still failing happened 21 minutes after Marc had merged the patch and our servers appliy configuration changes twice per hour (but distributed across the full 30 minute range to spread the load). You were simply unlucky :-)

hehe I was too impatient! :-) Thanks for the explanation.