Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.6] Fix the condition for logging empty JWK sets. (#91675) #91678

Merged
merged 1 commit into from
Nov 18, 2022

Conversation

ywangd
Copy link
Member

@ywangd ywangd commented Nov 18, 2022

Backports the following commits to 8.6:

The logic for check isEmpty should have been flipped. This PR fixes it.

Relates: elastic#91001
@ywangd ywangd added :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) >non-issue auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Security Meta label for security team labels Nov 18, 2022
@elasticsearchmachine elasticsearchmachine merged commit e7011ef into elastic:8.6 Nov 18, 2022
@ywangd ywangd deleted the backport/8.6/pr-91675 branch November 18, 2022 08:56
@ywangd ywangd added v8.6.0 and removed v8.6.1 labels Nov 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >non-issue :Security/Authentication Logging in, Usernames/passwords, Realms (Native/LDAP/AD/SAML/PKI/etc) Team:Security Meta label for security team v8.6.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants