Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Agreed in the Community meeting on the 29th of March 2022 and dev meeting from the 31st of March.

  • React UI work
    • Some work has occurred to replace the existing expired Egeria certificated with up to date valid certificates, as part of this, the certificates are validated.  
    • The Egeria React UI 3.7 introduced new environment variables to allow the user to provide their own pfx ca and passphrase.
    • Further work is being done to allow the pfx ca and passphrase to be specified per platform.
  •  The concern was raised that this sort of routing should not be the responsibility of the the deployer of the UI.

...

  • It would be more appropriate to use something like Ingenx or Istio to handle:
    • routing
    • authentication
    • certificates
  • there seems to be a need for both these approaches:
    • a manual approach allowing pocs, education and demos without requiring an overarching framework and a lot of enterprise orientated setup. This would run our node application.
    • an enterprise approach that would :
      • have a single authentication approach
      • remove routing from the React UI
      • remove the need for a node application.      
  • short term we enable ldap for the React UI (without multi tenancy)
  • we will address the 

 

Steps agreed in the TSC meeting on the 25th of January 2022. 

...