[Openid-specs-ab] Endpoint registration !?
ve7jtb at ve7jtb.com
Wed Dec 14 21:48:13 UTC 2011
The simplest thing would be to do it as claims.
That would then return them from the user_info endpoint as a reference giving you the endpoint URI, and an access token.
You could also define a scope that covered a bunch of claims as a group.
Probably publishing it as a profile is the best way to circulate it.
Those attributes in eduperson scema will also be of interest to US Gov agencies who are currently federating with InCommon.
On 2011-12-14, at 10:34 PM, Roland Hedberg wrote:
> At the EuroCAMP meeting yesterday and today we spent some time discussing OpenID Connect.
> Specially the second day when thanks to John and Nat's introduction day one people had a better grasp of the subject, a discussion on how OIC could be used in our (higher education) environment started.
> It was quite obvious that we for instance needed more and more varied identity information.
> So the (crazy?) idea came up that we would define a new endpoint beside the user-info endpoint, the eduPerson endpoint.
> Ideas about group/scim/authz endpoints also surfaced.
> Since I guess there is nothing that prevents us from defining one or more endpoint with different characteristics than the standard ones to be use in/by our community it still would be interesting to make them known to a bigger community.
> So, it brings up the question about registration of endpoint names and characteristics.
> Any thoughts about this ?
> -- Roland
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
More information about the Openid-specs-ab