Re: [OAUTH-WG] Comments on draft-ietf-oauth-json-web-token-05

2012-11-27 Thread Mike Jones
I'll add it to my to-do list to define "prn" as being globally unique. -- Mike From: John Bradley [mailto:ve7...@ve7jtb.com] Sent: Monday, November 26, 2012 11:04 AM To: Torsten Lodderstedt Cc: OAuth WG; Mike Jones; Nat Sakimura Subject:

Re: [OAUTH-WG] Comments on draft-ietf-oauth-json-web-token-05

2012-11-26 Thread John Bradley
I don't know that we need user_id in the JWT spec it may be enough to have it as a OIDC extension if it is not globally useful. I agree that the definition of prn should be more specific. On 2012-11-26, at 3:56 PM, Torsten Lodderstedt wrote: > Hi John, > > does it make sense to change the spec

Re: [OAUTH-WG] Comments on draft-ietf-oauth-json-web-token-05

2012-11-26 Thread Torsten Lodderstedt
Hi John, does it make sense to change the spec as follows: - specify the prn claim as being globally unqiue - add user_id as scoped by iss claim What do you think? regards, Torsten. Am 26.11.2012 19:51, schrieb John Bradley: A user_id is scoped to a iss. There is some notion that a prn is g

Re: [OAUTH-WG] Comments on draft-ietf-oauth-json-web-token-05

2012-11-26 Thread John Bradley
A user_id is scoped to a iss. There is some notion that a prn is globally unique, though the JWT spec is not clear on that. I think people are thinking of it like a UPN in LDAP/AD. John B. On 2012-11-26, at 3:46 PM, Torsten Lodderstedt wrote: > Hi John > > thanks for the explanatian. Just t

Re: [OAUTH-WG] Comments on draft-ietf-oauth-json-web-token-05

2012-11-26 Thread Torsten Lodderstedt
Hi John thanks for the explanatian. Just to make sure I got you right. A prn can be a user_id. A prn is bound to the scope of an iss. Regards, Torsten. John Bradley schrieb: >JWT is more generic than OIDC. > >prn and user_id as used by OIDC are similar. user_id is already in >wide use wit

Re: [OAUTH-WG] Comments on draft-ietf-oauth-json-web-token-05

2012-11-26 Thread John Bradley
JWT is more generic than OIDC. prn and user_id as used by OIDC are similar. user_id is already in wide use with Facebook's signed request. We were hoping that Facebook would be more likely to migrate from signed request to JWT if the parameter names stayed the same for developers. In the ge

[OAUTH-WG] Comments on draft-ietf-oauth-json-web-token-05

2012-11-24 Thread Torsten Lodderstedt
Hi, I've got a few comments on your draft. I’m wondering why neither acr nor auth_time (which are used in OIDC) made their way into this spec? What is the difference between prn and the user_id claim OIDC uses? regards, Torsten. ___ OAuth mailing