Shibboleth Developer's Meeting, 2020-02-07
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 2020-02-21. 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
- V4.0.0 beta release process
- Do we need all three hashes
- Use of maven.javadoc.failOnError=false for the actual deploy builds
- ???
- GCM default decision
Attendees:
Brent
Daniel
Henri
- java-idp-oidc-multi green on Jenkins
- Test failures were mostly related to test objects expiring too quickly
- One unintended dependency between two flow tests
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JOIDC-2 - The OP discovery/configuration flow customization can now be done via property-configurable bean
- Should we get rid of Webfinger flow for V2?
Ian
Marvin
Phil
- finished rippling out the new checked EncodingException to all 60 call sites (quite a few in test classes, which is easier to handle).Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key JSPT-93 - Ready to commit, today if sensible.
- There are 5 call sites - which I will list in the ticket once committed - that definitely need checking.
Rod
- Installer
- I18N
- SP 3.1 prep
Scott
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key SSPCPP-878 - Plan at the moment is that 3.1 upgrade will impact old Safari without explicit action
- Evaluating approaches to implementing SP request/response correlation
Tom
Other