Shibboleth Developer's Meeting, 2021-01-15
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-02-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
- Time to zap All Java 7 stuff in Jenkins? Please?
- WebID - anybody willing to represent us?
- SP planning
Attendees:
Brent
Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key OSJ-82 - Mostly done. The only remaining major piece is sorting out how the encryption configuration and parameters resolution pieces will work.
Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key OSJ-118 - Mostly done. Finalizing how we will deal with "metadata" about known and supported named curves. Right now there's a registry like the one we have for algorithm descriptors, loaded via the Service API.
...
- Proxying improvements
- Direct consumption of upstream Attributes for user identity, replaces awkward attribute resolver settings
- Hooks outbound and inbound to customize/validate messages
- Added MessageHandler that runs an injectable function, getting around the problem of declaring an "optional" MessageHandler, same trick could work for Actions
- Finished tabifying resolver and metadata docs
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1735 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key SUPPORT-218 - Possible JPA regression, particularly confused by exception leak
- SP call, put on agenda
Tom
- patching
- working on some AMI automation and Jenkins Pipeline research
...