Implement OAuth 2.0 Dynamic Client Registration Protocol

[jgrandja]

This feature will deliver OAuth 2.0 Dynamic Client Registration Protocol.

[pkostrzewa]

@jgrandja Can I pick this one?

[jgrandja]

Thanks for your interest @pkostrzewa.

This feature is currently on-hold (as indicated in the labels) and will likely not get implemented for a couple months at least.

OpenID Connect 1.0 Client Registration Endpoint gh-57 is the priority at the moment and the work has started in gh-189.

[uhhhh2]

@jgrandja Do I understand the status of this issue correctly?

• Create a registration: OIDC spec RFC Spring Authorization Server issue (done)
• Get a registration: OIDC spec RFC Spring Authorization Server issue (done)
• Update a registration: RFC Unable to find Spring Authorization Server issue (probably not started yet?)
• Delete a registration: RFC Unable to find Spring Authorization Server issue (probably not started yet?)

[jgrandja]

@uhhhh2 Yes, the first 2 items are completed.

The last 2 items refer to RFC 7592 OAuth 2.0 Dynamic Client Registration Management Protocol, which does not have any tickets open at the moment. And would be a low priority item anyway, as we have many more features that still need to be built that are high priority.

This specific ticket addresses RFC 7591 OAuth 2.0 Dynamic Client Registration Protocol, which is on-hold and is a low priority item as well.

[aphalke]

@jgrandja can you please let us know tentative release when we will get this? And what would be the alternative way as of now to register the client dynamically? Thanks in advance, Atul.

[jgrandja]

@aphalke OpenID Connect 1.0 Client Registration Endpoint has been implemented for a while now.

[proyupgrade]

@jgrandja Do I understand the status of this issue correctly?

• Create a registration: OIDC spec RFC Spring Authorization Server issue (done)
• Get a registration: OIDC spec RFC Spring Authorization Server issue (done)
• Update a registration: RFC Unable to find Spring Authorization Server issue (probably not started yet?)
• Delete a registration: RFC Unable to find Spring Authorization Server issue (probably not started yet?)

@jgrandja Do you guys have any update regarding the "client registration update" feature? We're looking on possibly creating our own converter to achieve this, but wanted to know first if the feature was on your short-time roadmap.

Thanks.

[jgrandja]

@proyupgrade The "Update a registration" feature is not on the roadmap. I'm not sure when it will be implemented as there are a few higher priority items ahead.

[oracle-fusion-middleware-team]

Now do we have DCR and DCR-M fully implemented (the "Update a registration" )? @jgrandja Just to confirm before implementing my own..

[jgrandja]

@oracle-fusion-middleware-team No it's not implemented. FYI, you can see the current feature list here.

[oracle-fusion-middleware-team]

Thanks for the info Joe, I'll go ahead implement my own.

[Suvink]

@oracle-fusion-middleware-team were you able to implement a workaround for update registrations?

[oracle-fusion-middleware-team]

@Suvink Nope, we eventually decided not to use dynamic registrations...

[dciarniello]

I've added my vote to this not for the basic dynamic registration but for the dynamic client registration management (RFC 7592).