Shibboleth Developer's Meeting, 2020-09-04
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 2020-09-18. 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
- Package sealing?
Attendees:
Brent
Daniel
Henri
Ian
John
Marvin
Phil
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-1595 - Functionally complete
- Bug fixing now (including the worrying
)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-1663 - Will swap in the module stuff and work on integrating it into the scripting plugins and the installer.
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-1666
Scott
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key SSPCPP-904 Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1671 - No longer need to teach it about new property files, we will auto-load anything under conf with that suffix.
Jira Legacy server Shibboleth JIRA serverId 180d847f-bce4-36b2-9964-771bff586829 key IDP-1664 - An IdPModule is a unit of function that can be individually enabled or disabled via command line.
- Plugins can expose any number of IdPModules after installation, and could auto-enable them.
- Generally this just involves managing a set of configuration resources by either copying them in or removing them (usually be saving them off, not deletion, but this will be controllable). Resources can be tagged as replace or noreplace, RPM-style.
- Most modules should be expressible with property files and a trivial subclass to add to the Java services file.
- Repeated enable/disable will be idempotent.
- "Disabled" modules may not be totally "off" but probably will operate with default, often unusable, settings.
- Many default config files (esp. for various subflows) will be removed or hidden in 4.1 behind disabled modules.
- Upgrades will act as though many modules are already enabled, and disabling them can be used to remove the files.
...