/
2025-08-01

2025-08-01

Shibboleth Developer's Meeting, 2025-08-01

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 2025-08-15. Any reason to deviate from this?

60 to 90 minute call window.

Call Details

This week's call will use the Zoom system at GU, see ZoomGU for access info.

AGENDA

  1. “Ratify” release plans for publicaton in response to Spring timelines

    1. Schedule 5.1.5 patch

    2. Targetting 5.2.0 once Spring 7 is final if SWF is compatible

  2. Board updates

Attendees:

Brent

 

Daniel

 

Henri

  • Back online this week

  • eduGAIN pilot has started

    • One Shibboleth test-OP ATM, couple interested deployers have contacted

    • Use cases are still very basic (e.g. no trust marks nor metadata policies)

  • https://shibboleth.atlassian.net/browse/JOIDC-222

    • Started improving / generalizing the trust chain resolution implementation

      • Currently more or less hardcoded for OIDC RP entities

      • Serves also the resolve entity API

Ian

 

John

  • Bumped image versions: Rocky 9, RHEL 8/9/10, AL 2/2023

  • Adjusted repo generation for Rocky & RHEL 10 (repodata now expected for SRPMs)

  • Working through scenarios for https://shibboleth.atlassian.net/browse/SSPCPP-993

    • Tagging strategy, overrides, multi-architecture, image presence detection, etc

Marvin

 

Phil

  • WebAuthn 1.3.0 released with new cache and JDBC accelerator

  • Moved onto OIDC SP.

 

Rod

  • Jetty Plugin

    • Writing/testing/rewriting the config scripts for windows & updating “documentation” in parallel

    • Getting prepared to tease jetty-base away from the plugin

    • Reverted to run against 5.1 and created tombstone classes for V5.2 (uniquely for it to use)

    • Open Question on truststore

      • Propose postponing discussion on that for 2 weeks.

 

Scott

  • Continued work on SP agent documentation

  • Some cleanup work deprecating some Apache commands on maint-3 branch and removing from main branch

    • Eventually will release SP 3.6 to carry all the warnings we need to insert, ways off at this point

Tom

Other