The concept is:
- A master account on Nasqueron, used for login at Auth Grove.
- A series of subaccounts to switch to, for example to be able to log in on a gaming bulletin board under several characters identity.
Description
Description
Revisions and Commits
Revisions and Commits
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T476 Implement subaccounts | |||
| Open | None | T477 E-mail processing for subaccounts |
Event Timeline
Comment Actions
Implementation
when the system is disabled, we create an identity with parameters matching the login one.
When the system is enabled, we create a first identity the same way.
See also Zed $CurrentPerso in addition to $CurrentUser.
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.