improve keycloak integration #62

Open
opened 2026-03-06 23:03:56 +00:00 by oxaliq · 4 comments
Contributor

i'd like to make keycloak integration more idiomatic (akin to integrating authentik as the OIDC provider.)

nextcloud maintains user_oidc app and recommends it as the default OIDC integration.

documentation for coop cloud's nextcloud recipe recommends oidc_login and configuration of nextcloud's config.php file. This is high touch, requiring changes made to the running container or maintaining the file in a local fork of the recipe and mounting the file as an EXTRA_VOLUME.

as a more idiomatic approach, a compose.keycloak.yml configuration could be used, in conjunction with changes to the keycloak recipe, to configure the integration via abra app config $DOMAIN and abra app secret generate ...

i'd love to take on this task based on what our coop has learned from deploying AIO nextcloud with ansible, but am proposing here first.

i'd like to make keycloak integration more idiomatic (akin to integrating authentik as the OIDC provider.) nextcloud maintains [user_oidc app](https://github.com/nextcloud/user_oidc) and recommends it as the default OIDC integration. documentation for coop cloud's nextcloud recipe recommends [oidc_login](https://github.com/pulsejet/nextcloud-oidc-login) and configuration of nextcloud's `config.php` file. This is high touch, requiring changes made to the running container or maintaining the file in a local fork of the recipe and mounting the file as an EXTRA_VOLUME. as a more idiomatic approach, a `compose.keycloak.yml` configuration could be used, in conjunction with changes to the keycloak recipe, to configure the integration via `abra app config $DOMAIN` and `abra app secret generate ...` i'd love to take on this task based on what our coop has learned from deploying AIO nextcloud with ansible, but am proposing here first.
Owner

Hell yeh @oxaliq, would love to see the PR!

Hell yeh @oxaliq, would love to see the PR!

@oxaliq Great! I also wanted to build this, but haven't had time yet. I was thinking, it should be possible to make this independent of Keycloak, right? Create a compose.user_oidc.yml to configure any OIDC provider? So this can also be used with e.g. Rauthy, not just Keycloak.

@oxaliq Great! I also wanted to build this, but haven't had time yet. I was thinking, it should be possible to make this independent of Keycloak, right? Create a compose.user_oidc.yml to configure any OIDC provider? So this can also be used with e.g. Rauthy, not just Keycloak.
Author
Contributor

hey! i have a PR i'd like to open (incorporating @dannygroenewegen 's suggestion to focus on the Nextcloud app rather than the OIDC provider.)
I don't seem to have permissions to push to a new branch in this repo, though.

remote: 
remote: error:
remote: error: User permission denied for writing.
remote: error:
To ssh://git.coopcloud.tech:2222/coop-cloud/nextcloud.git
 ! [remote rejected] user_oidc_setup -> user_oidc_setup (pre-receive hook declined)
error: failed to push some refs to 'ssh://git.coopcloud.tech:2222/coop-cloud/nextcloud.git'
hey! i have a PR i'd like to open (incorporating @dannygroenewegen 's suggestion to focus on the Nextcloud app rather than the OIDC provider.) I don't seem to have permissions to push to a new branch in this repo, though. ``` remote: remote: error: remote: error: User permission denied for writing. remote: error: To ssh://git.coopcloud.tech:2222/coop-cloud/nextcloud.git ! [remote rejected] user_oidc_setup -> user_oidc_setup (pre-receive hook declined) error: failed to push some refs to 'ssh://git.coopcloud.tech:2222/coop-cloud/nextcloud.git' ```

@oxaliq You can create a fork of the nextcloud repo, push the branch there, and use that for a PR.

@oxaliq You can create a fork of the nextcloud repo, push the branch there, and use that for a PR.
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/nextcloud#62
No description provided.