Couple to Kerberos accounts (OAuth)

[TomNaessens]

I imagine that in the future, linking Gamification and Tab would be a cool option. But therefore, we need to have a unique link between both.

[Procrat]

I think the first step in this would be to add the github names to LDAP.

[TomNaessens]

That isn't even necesarry. Tab uses the Zeus usernames. When someone logs into Gamification for the first time, he sould be redirected to the Zeus OAuth where he authenticates and gets redirected back to Gamification, where Gamification can automatically query his username through the API.

[iasoon]

We could also link Github and Zeus accounts ourselves, but I can imagine there are other uses for github names, so I'm with Procrat on this one.

[Procrat]

"query his username through the API"

Which API is this you're talking about? In your point of view, where does the connection between Zeus accounts and Github accounts happen?

[TomNaessens]

1. User logs in using Github
2. User gets redirected to a page with a button “Connect to Zeus kerberos account”
3. User clicks the button
4. User gets redirected to the OAuth interface, where he logs in with his Kerberos account
5. After a succesfull login, the user gets redirected back to Gamification
6. Gamification queries the API I made for Tab, returning the username (http://kelder.zeus.ugent.be/oauth/api/current_user/)
7. Gamification stores the username retrieved in a field in the User model

On 21 Mar 2015 at 12:37:46, Stijn Seghers (notifications@github.com) wrote:

"query his username through the API" Which API is this you're talking about? In your point of view, where does the connection between Zeus accounts and Github accounts happen?

— Reply to this email directly or view it on GitHub.

[TomNaessens]

In your scenario, how would you link the Github usernames to the LDAP?

[Procrat]

First of all, the prime reason for entering this in LDAP is, like @Iasoon mentioned, because we might indeed find other uses for this.

I was thinking about doing this manually, but on second thought, that doesn't appear to be a long term solution, simply due to the fact that a lot of new Zeus members won't have a GitHub account yet.

Maybe we can fabricate something that follows the flow like @Silox said, but effectively updates LDAP?

[TomNaessens]

That sounds good. You can do an API call (if I write the server-part) for that to set the github name to an ldap entry?

On 21 Mar 2015 at 16:56:04, Stijn Seghers (notifications@github.com) wrote:

First of all, the prime reason for entering this in LDAP is, like @Iasoon mentioned, because we might indeed find other uses for this.

I was thinking about doing this manually, but on second thought, that doesn't appear to be a long term solution, simply due to the fact that a lot of new Zeus members won't have a GitHub account yet.

Maybe we can fabricate something that follows the flow like @Silox said, but effectively updates LDAP?

— Reply to this email directly or view it on GitHub.

[iasoon]

Bumping this as a requirement for #87.