[Openid-specs-ab] Your help needed clarifying Google's "azp" claim usage

[Adam Dawes]

>From one of our engineers:

AFAIU, the only case where "azp" is different from "aud" is Android
cross-client ID token.
In that case, the azp is the ID token requestor, which is the Android app,
and the audience is the app's home server, for which the ID token is
intended.
Unfortunately, this underlying protocol is not standard OAuth2 or OIDC. I'm
not sure we want to publicly document the protocol traces.

On Wed, Aug 19, 2015 at 12:16 PM, Mike Jones <Michael.Jones at microsoft.com>
wrote:

> Hi Googlers,
>
>
>
> It would be hugely useful if you could capture protocol traces that
> demonstrate how Google actually uses the “azp” claim in cases where the
> “azp” and “aud” values differ.  Ideally, I'd like to see actual protocol
> traces, including the Authentication Request, the Authentication Response,
> and both directions of any the communication between the Client that made
> the request to the OP and any other Clients that it also sends the
> resulting token(s) to. Among other things, that would also answer OAuth-y
> questions like which Client ID is being used for client authentication to
> the OP when more than one client is involved.
>
>
>
> The Connect text about “azp” is currently both ambiguous and
> contradictory.  This data would be of a huge help to us for sorting this
> out during the current errata round.
>
>
>
>                                                                 Thanks a
> bunch,
>
>                                                                 -- Mike
>
>
>
> _______________________________________________
> Openid-specs-ab mailing list
> Openid-specs-ab at lists.openid.net
> http://lists.openid.net/mailman/listinfo/openid-specs-ab
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20150819/fd006d2e/attachment.html>