On 20/01/12 00:52, Monty Taylor wrote:
> It is on our todo list to use the team information from the OpenID
> response directly in gerrit. Once we do that, I can stop having to do
> the batch create of user accoutns in gerrit. However, that means a Java
> patch to Gerrit core, so it's probably not going to get done tomorrow. :)
>
> In terms of API additions, team info for a given OpenID identifier would
> not be useful - what I need is to get via the API is the OpenID
> identifier for a given user. If I could get that, I could stop
> screen-scraping.
A user doesn't have a unique OpenID identifier. They can have multiple
due to account merges, and eventually several from different providers.
We could possibly allow them to select the primary identity, but really
you should be looking things at authentication-time, not before.
On 20/01/12 00:52, Monty Taylor wrote:
> It is on our todo list to use the team information from the OpenID
> response directly in gerrit. Once we do that, I can stop having to do
> the batch create of user accoutns in gerrit. However, that means a Java
> patch to Gerrit core, so it's probably not going to get done tomorrow. :)
>
> In terms of API additions, team info for a given OpenID identifier would
> not be useful - what I need is to get via the API is the OpenID
> identifier for a given user. If I could get that, I could stop
> screen-scraping.
A user doesn't have a unique OpenID identifier. They can have multiple time, not before.
due to account merges, and eventually several from different providers.
We could possibly allow them to select the primary identity, but really
you should be looking things at authentication-