Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

Shibboleth Developer's Meeting, 2022-02-18

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 2022-03-04. 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

Add items for discussion here

  • Move to Amazon Corretto 17 to build Site? Have been using OpenJDK 15 to overcome the search.js bug in 11, but as that is EOL it makes sense to move to a supported version.

    • Tested it with Ian using his Docker image, works well.

    • Ian: The amazoncorretto-17 image is new and intended for IdP v5 et al; moving to it for this would allow us to zap the openjdk-site image.

  • Any reason not to move our minimum of maven to 3.8.4 ( GEN-308 - Getting issue details... STATUS )?

  • Thread-local storage risk on new containers? https://github.com/eclipse/jetty.project/issues/6973#issuecomment-940017697

Attendees:

Brent

  • JCOMOIDC-41 - Getting issue details... STATUS

    • pushed some draft code up to dev branch, comments in the ticket

  • OSJ-347 - Getting issue details... STATUS

  • OSJ-334 - Getting issue details... STATUS

    • Done.

Daniel

Henri

Ian

  • Java 18 now RC1.

  • Spring Framework 5.3.16 addresses SpEL issue ( IDP-1901 - Getting issue details... STATUS ).

John

Marvin

Phil

Rod

  • Supply chain defence:

    • All nightly builds now check all downloaded code jars against our keyrings

    • All distributions check the shipped jars against our keyrings

    • I believe that mvn versions:set is clean,

    • mvn site:site opens a whole new jar of worms GEN-310 - Getting issue details... STATUS

    • Are there other commands we need to worry about.

    • “Are we there yet?”

Scott

  • JOIDC-11 - Getting issue details... STATUS

    • I think functionally complete at this point, including encryption

    • Cleaned up some bad design choices, think this will extend naturally to the code grant

    • Settled on client as requester, token audience as proxied requester for consistency with OIDC

  • Added support for authenticated, unverified use of introspection/revocation

  • Long term think we should continue pushing toward authenticated, unverified clients for OIDC as well

Tom

Other

  • No labels