Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate dokuwiki away from Keycloak #3

Open
e1mo opened this issue Dec 30, 2022 · 1 comment
Open

Migrate dokuwiki away from Keycloak #3

e1mo opened this issue Dec 30, 2022 · 1 comment
Labels
enhancement New feature or request services/dokuwiki

Comments

@e1mo
Copy link
Member

e1mo commented Dec 30, 2022

Migrating away from Keycloak is, from a technical point of view, quite easy:

  1. Ensure users have valid E-Mail addresses in the Keycloak.
  2. Remove plugin.oauth.singleService. Users can now login with both Keycloak and plain auth and set a password for their plainauth user.
  3. After some time set authtype = "authplain" and remove/disable the oauth and oauthkeycloak plugin. Users which did not set a password in the previous step can trigger a password reset.

However, we somehow need to handle registrations for the Dokuwiki. Just leaving them open will (and did in the past) invite spam bots. Thus we need to decide with which (combination) of these options we want to take:

  • manual approval for write access (Add @confirmed ACL with ACL of upload or delete, no extra permissions @user)
  • Plugins like preregister, optionally with captcha (especially their honeypot support). However, accessibility is a concern.

What do we want to do in the end?

@dasPolygon
Copy link

we think manually approving users might actually be the best option.
We also can imagine feeling responsible for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request services/dokuwiki
Projects
None yet
Development

No branches or pull requests

2 participants