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 14 Next »

Shibboleth Developer's Meeting, 2024-12-06

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 2024-12-20. 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

Attendees:

Brent

  • JSSH-56 - Getting issue details... STATUS

    • Basically finished, along with parsers, except for wiki docs. Unless Scott still has concerns about defaults, etc.

  • JSATTR-6 - Getting issue details... STATUS

    • Substantially functionally done for the base SAML SSO (backchannel) case. Still pending are assertion validation (easy) subject match, and various strategy plugin impls.

Daniel

  • Nothing to report

Henri

  • Absent today (Finland Independence Day)

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

    • Playing and iterating details of metada policy, constraints and trust marks

Ian

  • Nothing to report.

John

Marvin

Phil

  • WebAuthn v1

    • Might need to work out how to test Windows Hello.

  • TechEx next week

Rod

  • Nothing

  • Tracking cpp-sp and windows build, but not ready for prime time yet (not even ready for the 3am slot actually)

Scott

  • TechEx slides

  • Gave notice I’d stop working on Xerces formally by mid-2025, to preserve my sanity and avoid prison

  • Continued SP work

    • Migrating and porting various utilities out of xmltooling library into SP library and namespace

    • Migrating to C++ standard locking primitives and interfaces

    • Porting and simplifying a class to support only local reloadable XML config, avoiding use of background threads due to lack of thread cancellation until C++20

  • Next milestone is to finish sanitizing all of Xerces and xmltooling out without losing fundamental “structure” of the existing code to allow further work inside various features, mostly requiring that the configuration machinery be fully re-implemented underneath all the components

.Tom

  • Rod - maybe reduce log level of the AttributeHelper ? From error to warn :

WARN [org.opensaml.profile.action.impl.LogEvent:94] - A non-proceed event occurred while processing the request: MessageExpired

ERROR [net.shibboleth.idp.ui.helper.AttributeHelper:109] - Attribute Context could not be located

ERROR [net.shibboleth.idp.ui.helper.AttributeHelper:132] - No Attribute Value found, returning ...

  • GEN-352 - Getting issue details... STATUS initial review of options, see comment on issue if you have any suggestions

Other

  • No labels