...
Jira Legacy server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSSH-56 Confirm thread pool behavior, per Scott.
Assuming looks OK, will do Spring parsers, etc.
Jira Legacy server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSATTR-6 Some progress made, still hoping to be functionally complete in a couple of weeks.
Daniel
Henri
Absent today
Jira Legacy server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-222 First more or less functional implementation for automatic registration in the authorize-flow
The RP metadata is fetched via oidfed trust chains and metadata gets stored via ClientInformationManager
Same method is used in the dynamic client registration flow - the RP records are stored server-side via configurable storage service
With automatic registration we should also provide means to avoid this server-side state (client secrets are never involved)
Test deployment plugged to the GEANT testbed - successful automatic registration of a test RP
Other upcoming work items:
Revisit our metadata policy implementation (in oidc-common)
It was done against much older oidfed-spec draft - the section in the spec has been reworked
Trust Marks
Explicit registration flow (i.e. oidfed-aware dynamic client registration flow)
Ian
RHEL 10 beta is out. I have set up an instance in the usual way (
r10avia the jump host, accepts anyiay.org.ukusers) for investigation.GA expected some time in the first half of 2025.
x86-64-v3!Wayland, if you care.
“modules” no longer used in the packaging system. Good.
GCC 14.2.
Default version of Java is OpenJDK 21.
See https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10-beta/
Spring Framework 6.1.15 and 6.2.0 are out. Just jump to the latter?
...