...
Decision on destroy methods in bean files - default it or explicitly set it?
(if time) Signing keys/supply chain attack defense
Attendees:
Brent
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSSH-16 Refactoring in progress. Large chunk of java-shib-shared done. Have to do a deeper dive into some changes around TLS.
Daniel
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1963
Henri
Offline today
Ian
Spring Framework 6.0.0-RC2 and Spring Boot 3.0.0-RC1 are out. GA will be next month. No statement on SWF yet.
MDA 0.10 in progress.
John
Updating Amazon Linux images
Fargate builder
Marvin
Phil
RP docs and code cleanup
Thinking about adding a keyset endpoint to the RP like the OP - a bit more involved than I thought, but perhaps should target this for v1?
Thinking about dynamic registration - but not confident I could get that in place for v1.
Thinking about UserInfo response formats - it can be either a plain JSON object or a JWT. Signalled by Content-Type header. But this could be manipulated, not sure this is much of a problem but I have added a setting to force JWT types only (off by default so supports either).
Fixed up the assembly, so can be installed as a plugin to a running IdP - tested it with a fresh plugin build and sign of the commons lib.
Rod
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-2025 Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1927
Scott
Xerces 3.2.4 patch
Likely officially moving project to requiring C++-11
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-2020 Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSSH-9 Overblown but we don’t reference impl classes anymore and I did modernize the Java random APIs
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-2023 Likely the biggest hassle for upgrades to V5
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1935 Worked around this issue for now, I think we want to open up more of the decryption APIs in V5 to be Criterion-based
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JPAR-213 Updated main branch for now, we’ll likely want to move the old branch to them alsoStill identifying some kind of issue with the logging classes referenced in webflows, loading the org.slf4j.LoggerFactory class is triggering an exception
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-2027
SP is being brought up to date after refactor, adding components for metadata, attribute handling
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-363 Will be working on new Session API next
Already built a remoted endpoint that parses XML and returns the DOM mapped into remotable objects so agents can deliver their configurations to the service for processing
...