668
edits
Identity/Verified Email Protocol/Latest: Difference between revisions
Jump to navigation
Jump to search
Identity/Verified Email Protocol/Latest (view source)
Revision as of 02:23, 2 November 2011
, 2 November 2011→Objects / Messages
(→Terms) |
|||
| Line 34: | Line 34: | ||
The Verified Email Protocol defines messages using the [http://www.ietf.org/dyn/wg/charter/jose-charter JOSE specifications] for signing JSON-formatted objects. | The Verified Email Protocol defines messages using the [http://www.ietf.org/dyn/wg/charter/jose-charter JOSE specifications] for signing JSON-formatted objects. | ||
=== Public Key === | === Public Key === | ||
| Line 49: | Line 42: | ||
* additional fields specified by the algorithm, e.g. ''n'' and ''e'' for RSA public keys. | * additional fields specified by the algorithm, e.g. ''n'' and ''e'' for RSA public keys. | ||
This | This data structure should move to [http://tools.ietf.org/html/draft-jones-json-web-key-01 JSON Web Keys]. | ||
=== Identity Certificate === | === Identity Certificate === | ||
| Line 67: | Line 60: | ||
{host: "intermediate.example.com"} | {host: "intermediate.example.com"} | ||
JOSE currently does not specify a certificate format. If it eventually does, we will consider moving to it. | |||
=== Identity Assertion === | |||
An Identity Assertion is a JWT with the following claims: | |||
* ''exp'' for expiration | |||
* ''aud'' for the relying party (audience.) | |||
== Relying Party Flow == | == Relying Party Flow == | ||