Shibboleth Developer's Meeting, 2020-03-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 2020-03-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
- Release planning.
- Agreement to freeze Monday 12am UTC, truly freeze Tuesday 12am UTC, start release process on Tuesday.
- OIDC will follow as soon as practical
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1580
- Post-release planning.
- Official V3 support through end of 2020
- No rush to branch, use feature branches for any doodling
- PS - Tomcat, Jetty, and Servlet Spec SameSite support summary if I am back in time.
Attendees:
Brent
- finish out some unit tests I skippedJira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1494
Daniel
Henri
- Couple bugs to be resolved for OIDC-plugin before release
- The most time consuming: https://github.com/CSCfi/shibboleth-idp-oidc-extension/issues/43
- Nimbus updated once again
Ian
Marvin
Phil
- Going to be 50 mins late due to Dr. Apt. will join when back to hopefully give summary on Jetty/Tomcat samesite hacks - info here.
Rod
- Watching V4
Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key EDS-72
Scott
- V4 testing and bugs
- SP misc
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key CPPOST-113
- Xerces shenanigans
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key INFRA-247
Tom
- OWASP Dependency-Check
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key INFRA-97 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1230 - add to parent POM ?
: so-far-so-good with low ulimit (1024) along with purging local snapshotsJira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1453 - Stop rather than terminate Windows EC2 instance ?
- related to
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key INFRA-246
- related to
- Reduced EC2 costs by testing only the RedHat supplied OpenJDK (instead of all JDKs) on RHEL8 instance.
Other