...
Calls are normally the 1st and 3rd Fridays of each month. :
Next call would
...
normally have been Friday 2024-12-20
...
but the decision was made to cancel this.
The first call of 2025, on 2025-01-03, may also be cancelled but we will decide that closer to the time.
60 to 90 minute call window.
...
Add items for discussion here
Attendees:
Brent
Jira Legacy server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSSH-56 Basically finished, along with parsers, except for wiki docs. Unless Scott still has concerns about defaults, etc.
Update: Reverted dynamic provider default to null/disabled like the rest.
Jira Legacy server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSATTR-6 Substantially functionally done for the base SAML SSO (backchannel) case. Still pending are assertion validation (easy) subject match, and various strategy plugin impls.
I will be out Dec 17 through Jan 8, so would miss the meeting on Jan 3 (and Dec 20, but sounds like it’s prob cancelled).
Daniel
Nothing to report
Henri
Absent today (Finland Independence Day)
Jira Legacy server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-222 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)
...
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 ...
initial review of options, see comment on issue if you have any suggestionsJira Legacy server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key GEN-352