Ping has an implementation that was done years ago but using a different parameter name (see 'aud' at https://documentation.pingidentity.com/pingfederate/pf92/index.shtml#adminGuide/tokenEndpoint.html for one example). So it's not this exact draft per se but is conceptually the same. And problems encountered using 'aud' as the name helped inform the direction of the draft. So it's very much related and running code and all that.
My understanding is that Microsoft has an implementation. I'm no authority on their stuff but, for example, you can see usage of the parameter in this documentation of the code flow: https://docs.microsoft.com/en-us/azure/active-directory/develop/v1-protocols-oauth-code On Fri, Jan 4, 2019 at 8:39 AM Rifaat Shekh-Yusef <rifaat.i...@gmail.com> wrote: > All, > > As part of the write-up for the Resource Indicators document, we are > looking for information about implementations for this document. > https://datatracker.ietf.org/doc/draft-ietf-oauth-resource-indicators/ > > Please, let us know if you are aware of any implementation for this draft.. > > Regards, > Rifaat & Hannes > _______________________________________________ > OAuth mailing list > OAuth@ietf.org > https://www.ietf.org/mailman/listinfo/oauth > -- _CONFIDENTIALITY NOTICE: This email may contain confidential and privileged material for the sole use of the intended recipient(s). Any review, use, distribution or disclosure by others is strictly prohibited. If you have received this communication in error, please notify the sender immediately by e-mail and delete the message and any file attachments from your computer. Thank you._
_______________________________________________ OAuth mailing list OAuth@ietf.org https://www.ietf.org/mailman/listinfo/oauth
