docs
docs copied to clipboard
[OIDC] Dynamic Client Registration (DCR)
WHAT Needs to be Documented?
- Dynamic Client Registration (DCR) support in ownCloud clients
- https://openid.net/specs/openid-connect-registration-1_0.html
- independent from server implementation (https://github.com/owncloud/openidconnect/issues/104#issuecomment-769886675)
- depends on
registration_endpoint
in/.well-known/openid-configuration
- ownCloud web: https://github.com/owncloud/web/pull/4286
- iOS: https://github.com/owncloud/ios-app/issues/865 (11.5+)
- Android: https://github.com/owncloud/android/issues/3054 (2.17+)
- Desktop: https://github.com/owncloud/client/pull/8350 (future 2.9+ release, can be tested with daily builds: ownCloud, testpilotcloud)
- Keycloak example config: https://github.com/owncloud/ocis/pull/1835
- Sadly not working with Kopano: https://github.com/owncloud/openidconnect/issues/142 UPDATE 22.05.17 by MM: this is no longer true, fixed on the Kopano side a year ago, see comment: https://github.com/owncloud/openidconnect/issues/142#issuecomment-1128737147
- Demo for testing and public accessible Keycloak UI for screenshots: https://owncloud.dev/ocis/deployment/continuous_deployment/#ocis-with-keycloak
WHERE Does This Need To Be Documented (Link)?
https://doc.owncloud.com/server/admin_manual/configuration/user/oidc/oidc.html
WHY Should This Change Be Made?
ownCloud clients learned Dynamic Client Registration (DCR). If IdP's support it, it makes admin life easier, because they don't need to add client ID & secret to their IdP configuration.
(Optional) What Type Of Content Change Is This?
- [x] New Content Addition
- [ ] Old Content Deprecation
- [ ] Existing Content Simplification
- [ ] Bug Fix to Existing Content
(Optional) Which Manual Does This Relate To?
- [x] Admin Manual
- [ ] Developer Manual
- [ ] User Manual
- [ ] Android
- [ ] iOS
- [ ] Branded Clients
- [ ] Desktop Client
- [ ] Other
Note after intense digging, that the Kopano issue regarding DCR has been solved. I edited the original post on top including a link.
@hodyroff you asked for effort estimation for this task @mmattel digged roughly in and the estimation is approx 50h