Page MenuHomeDevCentral

UndoStack
Open, HighPublic

Description

We've in D445 an UndoStore to represent an operation to undo.

Plan is to provide user session with a LIFO stack of undoable operations.

Items of this stack should ALSO be extractable by operation hash.

Finally, an implementation to store the stack in session for Symfony should be included.

Revisions and Commits

Event Timeline

dereckson removed dereckson as the assignee of this task.Feb 16 2023, 19:30

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.