...
Attendees:
Brent
Daniel
Henri
Jira Legacy server System Jira serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JOIDC-200 Currently no known issues
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
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?
...