Shibboleth Developer's Meeting, 2021-07-02
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-07-16. 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
- Atlassian provisioning options.
Attendees:
Brent
- Back from vacation. No progress to report. Next up is continuing to look at the Java socket server question.
Daniel
Henri
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key JOIDC-21 - High-level planning at: /wiki/spaces/DEV/pages/1213038673
- Functional PoC for the admin flow & CLI
- Access token encoding/encryption: the current method used for Authz codes and access/refresh tokens rely unnecessarily to Nimbus
Ian
- Java 17: now being tested in
-multi
jobs; all seems well.- Nashorn 15.3: "The most notable change is that Nashorn now works with JDK 17.", see see https://twitter.com/OpenJDK/status/1410603091490054166
- This is something to do with
Unsafe.defineAnonymousClass
I think, not clear why we aren't seeing issues in-multi
jobs.
- SKS (PGP/GPG) keyservers are defunct (RTBF/GDPR, apparently). Acronyms much?
...
added test, fixed, and deployed 1.1.1 of the Duo pluginJira 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 JDUO-47 - Maven cleanup
- we can get rid of our patched one from Nexus.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 JPAR-178
- thanks to the work Scott put in, I think this is done, other than testing (and some possible adjustment of server-side scripts) during a release.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 JPAR-176
- OIDC-RP
- Slow progress, hopefully have more time now the Maven stuff is done.
- Spent a small amount of time on Webfinger for OP discovery - can not see much support for this.
- The plugin probably should provide some support? to support OP discovery on the flow (like SAML proxying does with IdP disco).
- Strategy-based lookup for now.
- Test
Rod
Jira Legacy | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...