...
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-347 As suspected, these tests aren’t doing much except checking for a successful fetch. Should we switch to an InCommon target? Do Scott’s changes to proxy port 9000 to /mdq change this at all?
Daniel
Nothing to report.
Henri
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-72 Also related to the patch (3.0.4) released this week: only the desired/supported claims to be stored during the dynamic registration
Deployers can choose e.g. request_uris
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-21 Metadata policy resolution via file or remote endpoint now works
TODO: JWT access token, polishing and unit testing
...