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
RFC 7951 - OAuth 2.0 Dynamic Client Registration Protocol defines a protocol to register clients dynamically. This is useful to provide authentication for SPAs and other scenarios without backend that can't be trusted with client secrets, so authentication can be performed with a client_id unique to each instance.
The text was updated successfully, but these errors were encountered:
OpenEMR uses this library for our OAuth2 implementation and I've been investigating Unified Data Access Profiles (UDAP) https://www.udap.org/udap-dynamic-client-registration.html as a means of providing greater security guarantees for dynamic client registration. I'd prefer to have much of the UDAP implementation (error codes, responses, certificate chaining validation) built into oauth2-server library if possible. If I implemented this, would the project be open to a PR to bring this in?
If this isn't something you see as a need or desire to incorporate that's just fine and we will just keep it in our own project.
RFC 7951 - OAuth 2.0 Dynamic Client Registration Protocol defines a protocol to register clients dynamically. This is useful to provide authentication for SPAs and other scenarios without backend that can't be trusted with client secrets, so authentication can be performed with a client_id unique to each instance.
The text was updated successfully, but these errors were encountered: