4:01 p.m.
Attendees:
Roland, Giuseppe, Johan, Maximillian H, Scott, Ivan, Heather, Peter
Notes:
1 - GitHub review
a. OIDC - https://github.com/IdentityPython (JWTConnect-Python-OidcRP,
JWTConnect-Python-CryptoJWT, etc)
Latest version of oidcop released last week and another release is in the pipeline.
Roland has been working on OIDF certification for the idpy software. This has helped him
find several bugs and issues with the OIDF test suite; both OIDF and idpy code will be
improved when this is done. We should consider using the OIDF tests as well as the idpy
tests for some releases.
There will be another vote to move the OIDC federation to an Implementor's Draft.
There is hesitation to move it to a proposed standard until there are more implementations
in production. Note that eduTEAMS has this as a goal (after a better consent flow has been
developed in Satosa, device code flow, and proper support for token exchange).
Giuseppe released the Satosa OIDC front end as a third-party
application: https://github.com/UniversitaDellaCalabria/SATOSA-oidcop. There is one issue
reported re: offline scopes.
b. Satosa - https://github.com/IdentityPython/SATOSA
Some new fixes, but mostly minor things. There is a new option in the context object to
allow the front end to pass info to the backend re: the services requesting authn context.
Previously the backend did not know about that.
•
https://github.com/IdentityPython/SATOSA/commit/e7f281c2418902f3a00bed88b31…
The discovery service is now a microservice that works across protocols. With the ability
to have requests go to OPs, need to consider how to improve the UX because we don't
have the same metadata (name, logo) for OIDC entries. Probably need a proper JSON format
for the SAML metadata that can also work for OIDC OP metadata so that the services can be
treated the same way. Need to bring in Leif to discuss possibilities.
Users keep pressing the back button which presents an error page. The logs show that
something went through but "magically" you're back to a previous point
trying to do something you've already done. There is no server-side state, only the
cookie, but may want to set some checkpoints in the cookie. Then when the user hits
'back' we know because of what's in the cookie. Then we can do things like
present better error messages. Ivan still researching.
c. pySAML2 - https://github.com/IdentityPython/pysaml2
d. Any other project (pyFF, djangosaml2, etc)
2 - Discussion
Latest in browser work
• WebID has changed its name to Federated Credential Management API (FedCM)
- https://github.com/WICG/FedCM
• Note that the privacycg has a thread on OAuth being tracking
(https://github.com/privacycg/nav-tracking-mitigations/issues/16)
3 - AOB
For those of you at all involved in the IETF or who point to tools.ietf.org:
---
Last May we announced that tools.ietf.org would be wound down.
See https://mailarchive.ietf.org/arch/msg/ietf/0n-6EXEmkTp3Uv_vj-5Vnm3o0bo/.
In that announcement, we anticipated shutdown before IETF 111. That was over-ambitious,
but we are getting close to ready to complete the transition, and expect to finalize it
before IETF 113.
As expected, most functionality has moved to the datatracker. A few services have, or will
be, moved elsewhere.
We are tracking the moved services at https://github.com/ietf-tools/tools-transition-plan.
If there are features at tools.ietf.org that you find important that are not yet available
elsewhere or captured on that page, please send a note to tools-discuss at ietf.org. If
you are more comfortable doing so, send a note to me (lars at eggert.org) or to Robert
Sparks (rjsparks at nostrum.com)
• Scott K is moving away from consulting, but has several clients interested in Satosa,
pySAML2 support. Please contact him if interested in learning more.
Thanks! Heather