You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just wanted to let the Solid-OIDC team know that I'm currently working with Aaron Parecki to define an OAuth IETF I-D for client identifier metadata documents, or as they exist in Solid-OIDC Client ID Documents. I believe we're currently compatible with the prior-work done by Solid-OIDC, and we've also acknowledged the prior work you've done.
This allows them to be used in the wider OAuth community, outside of that of just Solid; for instance, in federated social media, where they are also quite useful, where OIDC Federation wouldn't necessarily work (due to lack of trust roots)
The text was updated successfully, but these errors were encountered:
I just wanted to let the Solid-OIDC team know that I'm currently working with Aaron Parecki to define an OAuth IETF I-D for client identifier metadata documents, or as they exist in Solid-OIDC Client ID Documents. I believe we're currently compatible with the prior-work done by Solid-OIDC, and we've also acknowledged the prior work you've done.
https://www.ietf.org/id/draft-parecki-oauth-client-id-metadata-document-01.html
This allows them to be used in the wider OAuth community, outside of that of just Solid; for instance, in federated social media, where they are also quite useful, where OIDC Federation wouldn't necessarily work (due to lack of trust roots)
The text was updated successfully, but these errors were encountered: