Page Comparison

...

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-200

  • Currently no known issues, initial profile documentation at OPPushedAuthorization

  • Jira Legacy
    server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-212

  • Jira Legacy
    server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-214

  • Jira Legacy
    server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-217

    • In short: with OAuth2 authorization requests, only use request object parameters. In OIDC, request object + query parameters can be merged.

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-201

  • Fine-tuning the refresh token sequence (differs a bit between confidential and public clients)

• Jira Legacy
  server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JCOMOIDC-115

  • Breaking change in Nimbus API makes old oidc-common (with Nimbus v10) incompatible

  • Jira Legacy
    server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-210

  • Should we make the upcoming idp.oidc.common.6 -module incompatible with the previous ones? IMHO it’d need patching for RP and Duo too in order to support new commons too? Or is it satisfactory to document that if a deployer updates the commons-module, also OP needs to be updated?

Ian

John

Marvin

Phil

Rod

• Jetty 12 MSI

• Question: Where are we ready to (pseudo) fork a maintenance branch (across all repos) and move mainline to the next minor?

...