More on data formats
dirkjan at ochtman.nl
Tue Nov 26 02:13:25 PST 2013
On Tue, Nov 26, 2013 at 10:46 AM, Shane Tomlinson
<stomlinson at mozilla.com> wrote:
> On 26/11/2013 02:17, Chris Karlof wrote:
>> Regarding how we signal the subject of the certificate, here's a summary
>> of where we're at:
>> For Persona certificates:
>> sub: <user's email address>
>> email: not used
> Does "email: not used" signify "is not present" or "is preset but
I think the consensus was that it would not be present.
>> For FxA certificates:
>> sub: <FxA user id as a uuid>
>> email: <verified email address supplied by user during signup>
>> Regarding how we represent the email/uid in the sub, since JWT allows
>> StringOrURI in the sub, we discussed using URIs to make the implied
>> semantics more explicit. For example, for FxA certificates, the sub could be
>> "urn:uuid:<FxA uid>", and for Persona certificates the sub could be
>> "mailto:<user's email address>".
> Was any decision made on whether the issuer or URI scheme will be used for a
> RP to differentiate the two?
Discussion was mostly around the verifier being able to differentiate,
not as much the RP, I think. In any case, it seemed to me like people
were uncomfortable about distinguishing based on the issuer, and
therefore wanted to add the scheme to make it easier. I must say that
I still don't fully grasp the perceived issue here.
More information about the Dev-fxacct