Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Jira Legacy
    serverSystem JIRA
    serverIdf52c7d31-6eab-3f0e-93c3-231b5754d506
    keyJOIDC-72

    • Initial version done: the claims that are included in the metadata policies (via profile config or access token) are stored

  • Jira Legacy
    serverSystem JIRA
    serverIdf52c7d31-6eab-3f0e-93c3-231b5754d506
    keyJOIDC-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
    serverSystem JIRA
    serverIdf52c7d31-6eab-3f0e-93c3-231b5754d506
    keyJOIDC-76

    • In principle it seems to be possible to add filter-mappings dynamically via ServletContextInitializer

Ian

  • Java 18 now RC1.

  • Spring Framework 5.3.16 addresses SpEL issue (

    Jira Legacy
    serverSystem JIRA
    serverIdf52c7d31-6eab-3f0e-93c3-231b5754d506
    keyIDP-1901
    ).

...