Shibboleth Developer's Meeting, 2021-05-21
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 2021-06-04. 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
Add items for discussion here
- Accept an external commit to update dependencies on OpenSAML maint-3 branch?
- Maven Central : we deploy OpenSAML V3 and V4 supply-chain ?
Attendees:
Brent
Daniel
Henri
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JOIDC-42 - All done! Preparing the paperwork
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JOIDC-47 - Found it during the cert tests - the bug has always been there, but now the test suite actually raised a warning
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JCOMOIDC-19 - Locked oauth2-oidc-sdk to 9.5.3 and jose-jwt to 9.9.3
...
- Started an oidc-rp authn plugin project
- Using the existing mpassid branch as a guide
- Can switch a decent amount to the oidc-commons lib of course
- Henri to teach me about using the OIDC test suite as an OP for testing.
- Maybe worth setting up a new gitolite repo for this?
- Similarly a JIRA project?
- Started a WebAuthn plugin project
- Too much to think about at this stage to need a repo and JIRA project I think.
- Some thoughts coming together on WebAuthn IdP Authentication Plugin
- Readying DuoOIDC plugin for 1.1.0
- Version compatibilityBug fix in oidc-commons leads to version compatibility changes?
Rod
Jira Legacy server Shibboleth JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1757 - New metadatagen command, Documentation pending
- Will offer to make a plugin (but quietly since noone seems to care)
- Completed
,Jira Legacy server Shibboleth JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1811
&Jira Legacy server Shibboleth JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1813
as per last meeting.Jira Legacy server Shibboleth JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1814 - Next up deprecations
,Jira Legacy server Shibboleth JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1787
(which will both be painful)Jira Legacy server Shibboleth JIRA columnIds issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1765 - Unless there is something more important needing attention?
...