4:18 p.m.
Notes from April 7 standing dev meeting
Attendees: Chris Phillips (CANARIE), Johan Peterson (SUNET)
Topics:
Continued review of code repo structure for v2.1.0 - MFA work
Discussion/table top thought experiment: ‘how sustainable are our technical design
decisions with the MFA items/approach?’
Notes:
JP+CP: reviewed the proposed Modular separation experiemental structure (ie use a separate
module)
Conclusion by mid mtg by JP+CP: not very sustainable because:
We would want to use this more intimately than a separate package
Eg. have MFA specific directives in the customizations and LocalManualSPSettings do
interesting things
Separate modules breeds unnecessary duplication of code (e.g. Write-host, logging, lang
packs etc)
Convergence is actually quite small and not unnatural
We already have assistive publish PowerShell items
Only adds 3 more public methods and an included dll, code base in git will have /src for
full transparency.
Next steps on this front
Johan opened ticket for work:
https://github.com/canariecaf/adfstoolkit/issues/127 ( Add the ability to support
RefedsMFA/SFA in the Toolkit )
Additional discussion about REFEDS MFA in a hybrid configuration was had
Alignment to REFEDS MFA behaviour was discussed If from our codebase trigger an MFA to do
the second factor trigger things, it will be more aligned to the REFEDS MFA
This is similar to the Freya technique
The ADFS operator has to apply the MFA rules specifically for the entity.
JP+CP discussed the techniques to apply the MFA as a way to test the sustainability of the
design