3:01 p.m.
Attendees
Heather, Ivan, JohnP, Hannah Sebuliba, Johan
Regrets:
Scott, Roland
0 - Agenda bash
New Incubator - GEANT has a program where they sponsor a team to do a project that will
serve as the basis to do something bigger. Niels suggested that we use the incubator
program to set up a matrix of idpy projects to determine if the communication is working
properly between all the different services. Ivan will send the suggestion about this to
the list. The trick will be that it's often the configuration, not the software
itself, that causes the problems. The matrix would need to be more about common
configurations rather than just a default deployment, but it's an open question as to
how what configurations we would choose. Ivan will follow up with initial meetings to see
if this can be applied to us, but this won't be a high priority and someone else may
want to eventually take point.
What if we started limiting support to specific profiles of configuration? The challenge
with that is we don't really know all the ways that idpy apps and libraries are used.
If we do go down this path, we'll need to document carefully because it will impact
what we test for, what issues are valid, etc.
1 - Governance policy updates
Board has approved the updated policies, with a few minor changes (specifying ideal test
coverage at 80%, requesting that the common incident handling policy is followed)
https://github.com/IdentityPython/Governance
2 - GitHub review
a. OIDC - https://github.com/IdentityPython (JWTConnect-Python-OidcRP,
JWTConnect-Python-CryptoJWT, etc)
No update
b. Satosa - https://github.com/IdentityPython/SATOSA
New release expected soon. We have a new contributor to the code base.
• https://github.com/IdentityPython/SATOSA/pull/354 - will be a breaking change for OIDC
plugins; see documentation
• will be some other updates to various microservices
c. pySAML2 - https://github.com/IdentityPython/pysaml2
Has just about finished the code that will let us update to new algorithms. Ivan will
merge the PR (https://github.com/IdentityPython/pysaml2/pull/778) soon, set up some new
GitHub actions (first time we'll be using these) and cut a new release.
Several people are working in the same part of the code, so we need to come to some
conclusion on the crypto pieces. Ivan will be reviewing the different PRs and figuring out
what and how to merge the ideas if not the exact code.
• https://github.com/IdentityPython/pysaml2/pull/781
• https://github.com/IdentityPython/pysaml2/pull/660
• https://github.com/IdentityPython/pysaml2/pull/787
Test Suite under development by Giuseppe: https://github.com/peppelinux/spid-sp-test. This
could serve as a way to start doing integration tests. The tests make certain assumptions,
which feeds the conversation about having specific support profiles (see Agenda Bash - New
Incubator discussion).
Next up for pySAML2:
1. More work around signing and encryption to add lists of allowed/disallowed algorithms
2. Creating a python-based signing/encryption library (replacing xmlsec1)
3. Changing the base of pySAML2 using a proper parser and possibly using types (idea
introduced by Davide Brunato)
d. pyFF - https://github.com/IdentityPython/pyFF
No update
Thanks! Heather