-
Notifications
You must be signed in to change notification settings - Fork 1
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
Change Authentication from LDAP to Keycloak #71
Comments
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 9, 2022
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 9, 2022
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 9, 2022
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 16, 2022
…ested) - adds commented version of future solution (based on a new authentication backen, without new models/cache nor improvement - leftovers to be removed once testing suite is (at least partially) complete Ref: #71
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 17, 2022
- updates backend so it considers minimal authentication parameters - updates unittests to consider more authentication flows Ref: #71
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 17, 2022
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 23, 2022
- keycloak UTs updates (based on new and improved flows) Ref: #71
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 23, 2022
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 23, 2022
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 28, 2022
oliveratfoodcoopx
added a commit
that referenced
this issue
Nov 30, 2022
- replaces print by self.stdout.write within command - replaces date.today calls by timezone ones in registration_view - adds test to check for username validation Ref: #71
oliveratfoodcoopx
added a commit
that referenced
this issue
Dec 1, 2022
before really switching to Keoycloak Ref: #71
oliveratfoodcoopx
added a commit
that referenced
this issue
Dec 7, 2022
oliveratfoodcoopx
added a commit
that referenced
this issue
Dec 7, 2022
oliveratfoodcoopx
added a commit
that referenced
this issue
Dec 19, 2022
- adds several tests to check for permissions within templates Ref: #71
oliveratfoodcoopx
added a commit
that referenced
this issue
Dec 19, 2022
oliveratfoodcoopx
added a commit
that referenced
this issue
Dec 22, 2022
- defines settings variable to control admin-related keycloak API Ref: #71
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
…ested) - adds commented version of future solution (based on a new authentication backen, without new models/cache nor improvement - leftovers to be removed once testing suite is (at least partially) complete Ref: #71
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
- updates backend so it considers minimal authentication parameters - updates unittests to consider more authentication flows Ref: #71
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
- keycloak UTs updates (based on new and improved flows) Ref: #71
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
- replaces print by self.stdout.write within command - replaces date.today calls by timezone ones in registration_view - adds test to check for username validation Ref: #71
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
before really switching to Keoycloak Ref: #71
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
- adds several tests to check for permissions within templates Ref: #71
mk2301
pushed a commit
that referenced
this issue
Jan 9, 2023
- defines settings variable to control admin-related keycloak API Ref: #71
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
…ested) - adds commented version of future solution (based on a new authentication backen, without new models/cache nor improvement - leftovers to be removed once testing suite is (at least partially) complete Ref: #71
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
- updates backend so it considers minimal authentication parameters - updates unittests to consider more authentication flows Ref: #71
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
- keycloak UTs updates (based on new and improved flows) Ref: #71
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
- replaces print by self.stdout.write within command - replaces date.today calls by timezone ones in registration_view - adds test to check for username validation Ref: #71
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
before really switching to Keoycloak Ref: #71
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
- adds several tests to check for permissions within templates Ref: #71
mk2301
pushed a commit
that referenced
this issue
Feb 1, 2023
- defines settings variable to control admin-related keycloak API Ref: #71
mk2301
pushed a commit
that referenced
this issue
Feb 16, 2023
mk2301
pushed a commit
that referenced
this issue
Feb 16, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As user and admin I want to have an authentication service and identity management which allows to have one user accout for several software application, use the email address instead of the derived user id from first and last name and be able to change the email address in self service.
To accomplish this (and it's general flexibility) we want to integrate the Keycloak server (https://www.keycloak.org/) into the Tapir project.
There is already some reusable code from MILA: https://github.com/MILA-Wien/collectivo/blob/main/collectivo/auth/middleware.py, but the account creation is still not done within Tapir but users are expected to create an account outside of Tapir. We need to do it during the registration wizard.
We can still use LDAP as the storage backend for Keycloak but this is not mandatory. If there are good reasons to use another backend this should be possible (this is anyway more a question of operation than development).
The text was updated successfully, but these errors were encountered: