Skip to content

OAuth 2 management UI: adopt a better approach to skipping optional metadata/context keys than #15148#15887

Merged
michaelklishin merged 1 commit intomainfrom
rabbitmq-server-15858
Mar 30, 2026
Merged

OAuth 2 management UI: adopt a better approach to skipping optional metadata/context keys than #15148#15887
michaelklishin merged 1 commit intomainfrom
rabbitmq-server-15858

Conversation

@michaelklishin
Copy link
Copy Markdown
Collaborator

Avoid comparisons to undefined by explicitly initializing the values to null.

Closes #15858.

@michaelklishin michaelklishin added this to the 4.4.0 milestone Mar 30, 2026
@michaelklishin michaelklishin changed the title OAuth 2: a better approach than #15148 OAuth 2 management UI: adopt a better approach than #15148 Mar 30, 2026
@michaelklishin michaelklishin merged commit b66f721 into main Mar 30, 2026
184 checks passed
@michaelklishin michaelklishin deleted the rabbitmq-server-15858 branch March 30, 2026 22:54
@michaelklishin michaelklishin changed the title OAuth 2 management UI: adopt a better approach than #15148 OAuth 2 management UI: adopt a better approach to skipping optional metadata/context keys than #15148 Mar 30, 2026
michaelklishin added a commit that referenced this pull request Mar 31, 2026
OAuth 2 management UI: adopt a better approach than #15148 (backport #15887)
michaelklishin added a commit that referenced this pull request Mar 31, 2026
OAuth 2 management UI: adopt a better approach than #15148 (backport #15887) (backport #15888)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

RabbitMQ 4.2.5 management login_oauth.ejs still throws ReferenceError: strict_auth_mechanism is not defined when no auth mechanism is provided

1 participant