...
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
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 also
Still identifying some kind of issue with the logging classes referenced in webflows, loading the org.slf4j.LoggerFactory class is triggering an exception
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
Tom
updating certs in integration tests for V5