Attendees:
Heather, Ivan, Roland, Scott, Peter, Christos, Giuseppe
Notes:
1 - GitHub review
a. OIDC -
https://github.com/IdentityPython (JWTConnect-Python-OidcRP,
JWTConnect-Python-CryptoJWT, etc)
The authors of draft-ietf-regext-rdap-openid are considering the use of the OIDC
Federation spec. Heather has put Roland/Giuseppe in touch with the authors.
All the libraries are being updated to make it through the OIDC test suite; oidcop is the
last one to be updated and is in final review. When this is complete, we can continue to
work such as development efforts around identity assurance (EKYC group). The interop work
is coming out of fintech. The verification of claims is related to the FAPI work; it's
one part. There is a client verifcation method called MTLS, but if you're an RP that
wants to use it, you have to be able to look at the certs used during the TLS
communication; that's not possible in the current libraries
(see
https://www.python-httpx.org/advanced/#ssl-certificates)
b. Satosa -
https://github.com/IdentityPython/SATOSA
Will be creating a new release for Satosa; various bug fixes.
Ivan has created a new label, "Next Release", which will tag issues and PRs that
will be merged into the next release so that people know what's coming next. Ivan
needs to go through the various issues to see if they need to be closed, moved, or whether
more work is needed.
Ivan is looking into GitHub actions; Travis is still having problems.
Satosa and the microservices interfaces being updated to support types; goal is to keep
the interfaces stable. Will do this via the data classes in pydantic. Hopes to expand this
into pySAML2. This is a low level change.
c. pySAML2 -
https://github.com/IdentityPython/pysaml2
New release available:
https://github.com/IdentityPython/pysaml2/releases/tag/v7.1.0
We now have proper support for verifying signatures for redirect bindings on incoming
authn and logout requests. See change log for more details.
There is a new capability to allow for on-demand metadata refresh. the endpoint is
implemented in Satosa, but not set up by default. Could a worker in Satosa's web
server be reserved for this? Ivan to look into having a separate queue to handle this
task.
d. Any other project (pyFF, djangosaml2, etc)
Giuseppe needs to update djangosaml2 with the latest pysaml2.
There is a scalability issue in the eduTEAMs space (OpenID front end and the oidc
libraries); they are passing JSON blobs up to 50Mb, which causes time outs. But since the
data structure must be what the library expects, it's hard to pull apart this blob. No
immediate solutions available.
Thanks! Heather