Shibboleth Developer's Meeting, 2023-07-07

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 2023-07-21. Any reason to deviate from this?

60 to 90 minute call window.

This week's call will use the Zoom system at GU.

Jenkins cleanup – should we just branch all the plugins at this point and get jobs cleaned up for everything?
1. We will rename the jobs to use the -v11 or -v17 suffix instead of using the product version.
2. We will branch all the plugins.
3. We will leave the V11 jobs in place (or create them again) and then create new V17 jobs.
Do we need to talk about Rocky (yet)?

https://shibboleth.atlassian.net/browse/OSJ-362
- Have implemented most of what is outlined in the issue.
- Still need to sort where/how the IdP function for the recipients is defined and will get injected into this new design.

Upgrading Duo to support IdP V5. Moving in Duo AuthAPI classes into the plugin
- https://shibboleth.atlassian.net/browse/JDUO-71
- https://shibboleth.atlassian.net/browse/JDUO-70
Moving work to Macbook temporarily. Setting that up with a V5 testbed to test changes above.

V5 bug fixing
Windows Installer:
- https://shibboleth.atlassian.net/browse/IDP-2140 Blocker for V5
- https://shibboleth.atlassian.net/browse/IDP-2136 Desired for V5
- Some changes rolled back into the mainline installer
  - Write the password for the P12 back-channel store we generate to secrets.properties
  - Do no prompt for passwords for the Key material. Generate 32 bytes of randomeness and Base64 that
- Looking to reduce our dependence on no-standard jetty stuff (not required for V5)
  - Windows has a forked jetty-ssl-context.xml
  - We have a mod/xml pair for back channel
  - And then there is the access log xml
- Magical jetty “Plugin”. Nice but not for V5
https://shibboleth.atlassian.net/browse/JJDBC-19 Case has gone quiet. Anybody in a position to reproduce (postgresssql)