Page Comparison

...

Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDC-72
- Initial version done: the claims that are included in the metadata policies (via profile config or access token) are stored
Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDC-21
- Initial version of the issue-registration-token admin-flow and CLI pushed
  - Opaque access token only for now - security configuration wiring for JWT access tokens was not trivial
- TODO:
  - Try different AdminFlow authentication approaches in practise
  - Wire authentication metadata (acr, principal) to the registration access token
Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDC-76
- In principle it seems to be possible to add filter-mappings dynamically via ServletContextInitializer

...

Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JCOMOIDC-40
- Have something for decoding unscoped strings. Will review and push next week. Other info in the ticket.
Jira Legacy
server System JIRA
serverId f52c7d31-6eab-3f0e-93c3-231b5754d506
key JOIDCRP-10
- Switching the arbitrary client metadata method of registering RP->OP config, to RP profile config.
Other
- UserInfo claims lookup, validation, and merge with id_token claims done.
  - Should support Plain JSON UserInfo response objects along with signed and or encrypted JWTs - when I plugin the TrustEngine.
- Added attribute filtering after transcoding to the validation stage before claims are exposed as Attribute Principals to the wider IdP.
- I will work with Tom soon to add RP to Jenkins.
- Might need a new Git repo for the SWF test classes that are now shared between the Duo plugin and the RP plugin. Something like java-spring-webflow-tests
  - Although it might not be useful to other plugins

...

Versions Compared