...
Add items for discussion here
Attendees:
Brent
Completed most backlog of 5.x issues, notably:
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-293 Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-307 Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-354 Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-372 Although will have to update some things if/when Santuario changes to the new methodology of using only algorithm name of “RSASSA-PSS”. That probably won’t come out before our 5.0 release - unless we do the work and then get them to do a release quickly.
A couple of the HC ones are still open for some docs and final review.
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSATTR-6 Probably won’t make 5.0, will likely re-schedule for 5.1. (Unfortunately missed awhile back b/c I didn’t have my Jira filter for 5.0 setup correctly after the project splits.)
Will start some work on it, maybe will be easier than it appears.
Assuming this is somewhat lower in priority now that Java SP is currently de-prioritized, right?
Daniel
Cannot attend the call today
cryptacular and ldaptive releases finished
Need to finish configuration work for startTLSResponseTimeout and autoReconnect for both authn and resolver to wrap up
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1963
Henri
Cannot attend the call today
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-161 The use of metadata policy -concept seems to be the way to go
This task hopefully finished next week
Ian
IdP: Dependencies upon dependencies. Most important ones now resolved, I think.
Java 21 is at Release Candidate; GA is 2023-09-19.
Spring Framework 6.0.12 expected 2023-09-14.
Spring Framework 6.1.0-RC1 also expected 2023-09-14.
John
Absent
Marvin
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1473 Commit hopefully by next week.
Phil
Not soo much.
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDCRP-44 Took a bit of time. Mucked a test, and fixed it. Tested against the cert suite.
Will look at Duo.
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDCRP-42 The issue was how
InetAddress.getByName("localhost").getCanonicalHostName();
returned an IP address on Windows but DNS name on Mac/Linux. This affected the SAN in the certificate the MockServer was using, the IP address version did not pass hostname verification.
Will get back to RP features.
Rod
IdP Beta
Scott
Beta and docs