[Openid-specs-ab] Spec call notes 5-Nov-12
Richer, Justin P.
jricher at mitre.org
Tue Nov 6 15:18:43 UTC 2012
We'll be following a similar approach, with the hope that the generic OAuth2 stuff will be pulled into the SECOAUTH library that our OIDC code is built on top of. Right now, this does mean a breaking change of a few items:
- changed the "type" parameter to "operation"
- changed the "application_name" parameter to "client_name"
- added several more optional parameters and return values (from the UMA draft)
There will probably be more items of this nature when the OAuth WG starts to really chew on it.
On Nov 6, 2012, at 10:13 AM, Roland Hedberg wrote:
> 6 nov 2012 kl. 14:50 skrev "Richer, Justin P." <jricher at mitre.org>:
>> That approach makes sense - I created a new issue for alignment with the OAuth2 spec, and that can be the issue that tracks this change. I agree completely with the "break it only once" mindset, with the idea that if you're going to break it anyway, make sure you break it *right* so that you don't have to break it *again*.
> As an exercise I'll implement the OAuth2 registration draft in the OAuth2 part of my OIC implementation.
> This would allow me to very straight forward see how a profiling could/should be done.
> Given that whatever the OAuth2 registration draft ends up as won't change what we (want to) have in OIC.
> -- Roland
> Roland Hedberg
> IT Architect/Senior Researcher
> ICT Services and System Development (ITS)
> Umeå University
> SE-901 87 Umeå, Sweden
> Phone +46 90 786 68 44
> Mobile +46 70 696 68 44
More information about the Openid-specs-ab