...
Jira Legacy server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JSATTR-6 Just before leaving on winter break ran into a (hopefully minor) problem with adding Assertion validation. Existing code is built on use of ProfileRequestContext. Hopefully can just widen that to InOutOperationContext, which should fit this new use case.
Daniel
Nothing to report
Henri
Jira Legacy server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-222 Current status for automatic registration PoC in the authorization endpoint
Trust chain resolution via metadata caches
Selection of the shortest local policy -compliant trust chain (via customizable function)
Trust Mark requirements may be configured on per Trust Anchor basis (OIDFED.AutomaticRegistration profile)
Metadata is currently stored via similar StorageService-backed ClientInformationManager as in dynamic client registration
Currently finishing PoC on an alternative that avoids storage by basing on metadata caches on all endpoints
Authorization code and access/refresh token claims sets carry the selected trust chain
Other work items:
Metadata policy handling
Null handling, minor operator changes (add/value at least), order of custom operators
Explicit registration - especially if considered important by community
Federation policy constraints
Test automation - my local tests currently exploits GEANT testbed
...