Shibboleth Developer's Meeting, 2020-03-20
Call Administrivia
09:00 Central US / 10:00 Eastern US / 14:00 UK / 16:00 FI
Calls are normally the 1st and 3rd Fridays of each month. Next call would be Friday 2020-04-03. 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 access info.
AGENDA
- AI for somebody to redeploy the IdP site and check the javadocs
- Work left on testing infrastructure?
- Development priorities
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key OSJ-82 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1473 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1454 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1392 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1126 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1014 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1015 - Duo / OIDC plugin, I think no issue filed yet
Attendees:
Brent
Daniel
Henri
- No development after OIDC v2 yet
- Planning to continue OIDC/SAML metadata work again next week (on hold since Dec)
- New feature branch or change master to 2.1.0-SNAPSHOT?
- If we want to use XML namespace urn:mace:shibboleth:metadata:*, XMLObject -related stuff should probably go to idp-saml-api + -impl?
...