Shibboleth Developer's Meeting, 2019-08-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 16th. 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
(Rod)Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1472 - Do we have a definitive list
- What to do about Transcoders?
Jira Legacy server Shibboleth JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1181 - See my summary (Rod)
- Where do we want fast fail to end up?
...
- Do we care about reloading metadata providers at depth > 1 (this thread)
- Installation
- Technologies? Our requirements are fixed, but there must be a better least worst technlogy
- Greater user control.
Scott
Tom
- AWS work continues
- worked through : Java updates, resizing storage, OS updates
- working on integration-tests multi-config jobs (Jetty 9.3/9.4 for IdPV3/V4)
- leaning towards one-Java-per-OS in AWS
- just easier to update on Linux
- i.e. run Amazon Linux rather than install Coretto on RedHat/CentOS
- Windows ?
- just easier to update on Linux
Other