1135884 - Give all localizers access to tableau_users (scm_l10n and @localizers), automate Tableau accounts for all LDAP logins

Status: RESOLVED INCOMPLETE

(Infrastructure & Operations :: Infrastructure: LDAP, task)

Description

[Axel Hecht [:Pike]]

Jabba said in bug 1135504 comment 4:

I've created the account and added to tableau_users. I'm not sure if there is any way to easily automate all members of @localizers to the tableau_users group, since one is an SVN authz group, and the other is an LDAP group. I suggest a separate bug to either do a one-time import into LDAP or to figure out some way to automate, but I think automating would be a difficult process.

I think getting a one-off for this is a good start. It'd be great if we could automate this, but then again, the few people that can vouch for access to either group can also just remember to add the tableau access request.

Comment 1

[Justin Dow [:jabba]]

There are 290 members of scm_l10n and 250 people in the svn @localizers group. I haven't yet created an intersecting list, but I imagine the total number might be a little smaller than the sum. I can work on creating an ldif to add them to the tableau_users group.

:sheeri - I think all of these users would need to be created in tableau as well? If you can remind me of the .csv format required, I can try to generate a csv for you to import into tableau once I have the final import list.

Comment 2

[Ludovic Hirlimann [:Usul]]

AFAIK we never clean the svn group so many might be inactive and might not need tableau access

Comment 3

[Sheeri Cabral [:sheeri]]

:jabba - I'd have to refresh myself on the import too - what I need from you is the email address and then the full name, comma-separated. The rest is all the same. I will do the import and document the format on a mana page (I should have done that 2 weeks ago when I did an import of about 60 localizers who used to receive weekly e-mails!)

Comment 4

[Axel Hecht [:Pike]]

I think there are two different things here:

Localizers getting localizer reports being one, and I guess that's a list kept in tableau or a data store close to  it? It'd be interesting to know for me which data items we still use for that.

The other is having localizers being able to browse the dataviz.m.o site and find data themselves. I would expect that one to be just within ldap? And that's the one I'd like to tackle in this bug.

Comment 5

[Sheeri Cabral [:sheeri]]

Just being able to login to the dataviz.m.o requires LDAP authentication and a Tableau account, which is what I need the CSV for.

There's a Tableau administrator's list of who gets what report and when - that'd be for another bug, it might be something we can share, but we'd have to research it.

Comment 6

[Sheeri Cabral [:sheeri]]

(In reply to Sheeri Cabral [:sheeri] from comment #3)
> :jabba - I'd have to refresh myself on the import too - what I need from you
> is the email address and then the full name, comma-separated. The rest is
> all the same. I will do the import and document the format on a mana page (I
> should have done that 2 weeks ago when I did an import of about 60
> localizers who used to receive weekly e-mails!)

The docs for this are at - 
http://onlinehelp.tableau.com/current/server/en-us/help.htm#csvguidelines.htm

We'd have to test to make sure that the right permissions are being set automatically - e.g. all users can see localizations but not it/finance/other graphs.

Comment 7

[Justin Dow [:jabba]]

Just an FYI. We are currently doing some evaluation on the levels of service we are using Okta for (Okta is currently used for logging into Tableau) and there might be some changes coming in Q1 around this, that would likely affect this bug, so I'd like to hold until Q1 on any action here.

Comment 8

[Sheeri Cabral [:sheeri]]

Have there been any changes in Q1 that affect this bug? It would be great to move on, so there's less manual work to be done.

Comment 9

[Justin Dow [:jabba]]

It's unclear to me if there is still action required here. I believe the stuff in comment 7 was referring to some additional work around Okta and tableau automation. It's an old bug and different people are working with tableau now. I'll close this preemptively, but feel free to re-open with a current request, and we should be better equipped now to handle it.