...
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
...