Page MenuHomeDevCentral
Create Task
Maniphest T1399

Migrate from globalfunctions to OmniTools
Open, LowPublic
Actions

Description

All globalfunctions (rKGF) functions are now wrappers to omnitools (rKOT).

Auth Grove uses the mb_str_pad and get_remote_addr methods from rKGF.

Instead, we should use rKOT as direct dependency.

  • to replace get_remote_addr, we can use Request::getRemoteAddress() or import the WithRemoteAdresse trait in a custom Request class extending the Laravel one (which itself extends the Symfony one).
  • mb_str_pad() is now Keruald\OmniTools\Strings\Multibyte\StringUtils::pad()

Related Objects
Search...

StatusSubtypeAssignedTask
 OpenNoneT1394 Deprecate Keruald global functions
 OpenNoneT1399 Migrate from globalfunctions to OmniTools

Event Timeline

dereckson triaged this task as Low priority.Apr 21 2018, 01:41
dereckson created this task.
dereckson added a project: Technical debt.
dereckson moved this task from Backlog to Dev on the Technical debt board.
dereckson moved this task from Backlog to Debt on the Keruald board.Feb 16 2020, 04:22
dereckson renamed this task from Migrate globalfunctions calls to OmniTools to Migrate from globalfunctions to OmniTools.Feb 19 2022, 11:28
dereckson updated the task description. (Show Details)
dereckson moved this task from Debt to Apps using Keruald on the Keruald board.
dereckson added a comment.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.

Nasqueron DevCentral · If it had been much bigger the moon would have had a core of ice. · Powered by Phabricator