Shibboleth Developer's Meeting, 2019-12-06
Call Administrivia
09:00 Central US / 10:00 Eastern US / 15:00 UK / 17:00 FI
Calls are normally the 1st and 3rd Fridays of each month. Next call would be Friday 2019-12-20. Any reason to deviate from this?
60 to 90 minute call window.
This week's call will use the Zoom system at GU, see ZoomGU for see ZoomGU for access info.
AGENDA
Add items for discussion here
- Decision on handling LDAP config
- Null handling in marshallers - expected behavior?
- Schedule for beta -
- https://issues.shibboleth.net/jira/issues/?filter=12673 (all cases, not including JPAR)
- https://issues.shibboleth.net/jira/issues/?filter=13370 (including JPAR, excluding closed & resolved)
- Create new long-running JIRA issues for 2020 (Tom)
- JPAR-56
- other maintenance tasks
Attendees:
Brent
- Working on SAML Proxy flow Response handling and Assertion validation
Daniel
- Ldaptive and LDAP configuration changes for v4
Henri
Ian
- <Dependency hell> x <Maven> = ?
- Lots of MDA work being done in UKf context
Marvin
Phil
- Flying to I2 TechEx tomorrow with Rhys, so can not attend.
- Started some deployer docs for CSRF. Only just added it, needs much work: Cross-Site Request Forgery (CSRF) Protection
- Have a question around how to expose user space configuration points - or if that is even wanted in this case. Will send an email or maybe speak to people (Scott) when in the US.
Rod
Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1179 - Can we please start testing the installer, in particular upgrades? Feedback needed on
- Functionality
- Logging
Thanks
Scott
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key OSJ-291 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key OSJ-293
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1494 - Moved SAML to top-level login flow and discovery (optionally) wired into all flows through a property signal
- Proxy controls done in both directions
- Think most of the needed options are done except for any security related ones
- Think all the likely necessary Issuer-based filter functions are done and documented
- Working on docs
- Need to get attribute transcoding rules done for all the eduPerson attributes
...