...
Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key SSPCPP-954
Marvin
Phil
- merged in the feature branch (dev/JCOMOIDC-41)Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JCOMOIDC-49 Took a bit of time, a thank you to Henri for testing the OP against it before the merge.
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JCOMOIDC-48 SSPCPP-954
Marvin
...
- moved the RP profile and security config over locally, which obviously works fine for just the RP, but a much bigger job when considering the OP profile and relying party config.
More wiki docs and more RP flow bean cleanup.
Was mistakenly worried about an old JWT key confusion attack (CVE-2016-10555). In the end, the vulnerability is from a particular library that is just bizarrely coded.
Rod
Cleanup - Notably
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSSH-5 Now looking at
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key IDP-1927 Engaging with JISC and Canarie Support Team on requirements
Nature study under way
...