Shibboleth Developer's Meeting, 2020-04-03
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-04-17. 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
- Ian Young: Branch-based development:
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key INFRA-250 - Former user (Deleted) If there is appetite, Javadoc and maven-javadoc issues - this will likely resurface for any subsequent release.
Add items for discussion here
Attendees:
Brent
Daniel
Henri
- Restarted the OIDC/SAML metadata work
- Ticket for tracking
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JOIDC-5
- Ticket for tracking
Ian
Marvin
Phil
- Sadly, only Javadoc issues. Including
andJira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key JPAR-161
along with many others...Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key JPAR-162 - Moving to DUO OIDC MFA plugin from next Tuesday.
Rod
- JSPT-95 and JSPT-96
- My plan is to wait for a nashhorn-free JDK and then prove that it works.
- I'll stall pushing to master until we are ready to consider IDP4.1
- I'll stall pushing to a dev branch pending today's agenda.
Scott
- SP beta
- EC2 build VM ready to use for release
- Prepping Xerces patch next week
- CentOS 8 working now in OBS for some random reason
- feature branchJira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JSPT-94 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JSPT-80 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key OSJ-246 - XML version nearing testability to compare storage size
- Server move on hold waiting for a CentOS 8 AMI, alternative approaches didn't pan out well.
- Contingency is probably Debian or Ubuntu
Tom
- not much
- moved commit rebuild jobs to EC2
Other