:08 PM
To: oauth
Subject: [OAUTH-WG] JWT Destination Claim
Here are the slides that I rushed though at the end of the Dallas meeting:
https://www.ietf.org/proceedings/92/slides/slides-92-oauth-1.pdf
And the -00 draft:
http://tools.ietf.org/html/draft-campbell-oauth-dst4jwt-00
In an informal
*Subject:* [OAUTH-WG] JWT Destination Claim
Here are the slides that I rushed though at the end of the Dallas meeting:
https://www.ietf.org/proceedings/92/slides/slides-92-oauth-1.pdf
And the -00 draft:
http://tools.ietf.org/html/draft-campbell-oauth-dst4jwt-00
In an informal discussion
Here are the slides that I rushed though at the end of the Dallas meeting:
https://www.ietf.org/proceedings/92/slides/slides-92-oauth-1.pdf
And the -00 draft:
http://tools.ietf.org/html/draft-campbell-oauth-dst4jwt-00
In an informal discussion earlier this week John B. suggested that some
...@pingidentity.com
Sent: 3/25/2015 2:19 PM
To: Mike Jonesmailto:michael.jo...@microsoft.com
Cc: oauthmailto:oauth@ietf.org
Subject: Re: [OAUTH-WG] JWT Destination Claim
FWIW, I did have that as an open issue in the draft:
http://tools.ietf.org/html/draft-campbell-oauth-dst4jwt-00#appendix-A
Though
from my Windows Phone
--
From: Brian Campbell bcampb...@pingidentity.com
Sent: 3/25/2015 2:19 PM
To: Mike Jones michael.jo...@microsoft.com
Cc: oauth oauth@ietf.org
Subject: Re: [OAUTH-WG] JWT Destination Claim
FWIW, I did have that as an open issue in the draft
