We also need to authenticate users against external sources.
Description
Description
Revisions and Commits
Revisions and Commits
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T336 Add login capabilities through external services | |||
| Open | None | T337 Authenticate users through OpenID | |||
| Open | None | T338 Authenticate users against GitHub | |||
| Resolved | dereckson | T882 Integrate Laravel Socialite code | |||
| Open | None | T339 Authenticate users against Facebook | |||
| Wontfix | dereckson | T340 Authenticate users against Twitter | |||
| Open | None | T341 Authenticate users against BitBucket | |||
| Open | None | T342 Authenticate users against Google | |||
| Open | None | T668 E-mail authentification |
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.