8 a.m.
On 18 Jul 2023, at 15:59, Heather Flanagan
<hlflanagan(a)sphericalcowgroup.com> wrote:
a. General
eduTEAMS: there has been contact with GEANT working on technical docs and they will be
helping with documentation for the front end. The team is also looking at connecting the
front end (idpy-oidc) with a postgres database, and part of the database are the secrets
for the connected clients. Team needs to properly hash the passwords before storing them.
Also, have been seeing some strange behavior that has to do with how state is kept within
the front end, but probably idpy-oidc. Should be having code that is loading in memory,
but when we restart a node, the information is lost. Once that is solved, everything is in
place for eduTEAMS code to go public.
Roland: when it came to storing info over time, decided nothing should happen by
'magic'. If you want to save something, you have to initiate that. If you
don't do that, then nothing is stored. This was a design decision early on.
Some additional information: There are methods/functions that can serialise class
instances to a JSON representation that can easily be stored in a database.
There are also methods/functions that can take the JSON representation and initiate class
instances from it.
This works for class instances in class instances in class … until basic types are
reached.
— Roland