improve keycloak integration #62
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.phpfile. 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.ymlconfiguration could be used, in conjunction with changes to the keycloak recipe, to configure the integration viaabra app config $DOMAINandabra 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.
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.
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.
@oxaliq You can create a fork of the nextcloud repo, push the branch there, and use that for a PR.