We should offer to:
- reset the password
- relink to another social provider if password auth isn't possible
- add hooks for more complex two-auths reset workflows as plugins
- display specific technical support instructions set for the installation
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T468 Add account reset feature | |||
| Open | None | T471 Password reset token is only verified after a form with password is submitted | |||
| Open | None | T472 [Route] Print an error message on /auth/reset instead of return a 404. | |||
| Resolved | None | T482 [CLI] Reset password command |
Event Timeline
Comment Actions
Development moratoire
Per T1771, we're currently considering implementing Keycloak as a reference identity management and SSO login product.
This product exposes a LDAP, OIDC (OpenID Connect) and SAML capabilities to authenticate users and applications. It seems to solve our main problems.
From there, it's not clear what we do with Auth Grove:
- Scenario A. We drop it, and as users we directly interact with Keycloak. Development is discontinued.
- Scenario B. Auth Grove is morphed into a front-end to use Keycloak: we expose current information, and interact with Keycloak API (through a generic set of classes to allow to switch to another solution) to set credentials and metadata.
- Scenario C. We use both Keycloak AND Auth Grove. We don't make integrate with Keycloak at all, to stay independent and not vendor-locked.
While T1771 evaluation is ongoing, a moratoire covers any development activities related to Auth Grove, with the obvious exception of security issues.
This moratoire cover fully or partly this task.