Fix AD realm additional metadata #47179
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
albertzaharovits
added
>bug
:Security/Authentication
Collaborator
|
Pinging @elastic/es-security |
bizybot
approved these changes
Oct 1, 2019
albertzaharovits
added a commit
to albertzaharovits/elasticsearch
that referenced
this pull request
Oct 1, 2019
Due to a regression bug the metadata Active Directory realm setting is ignored (it works correctly for the LDAP realm type). This commit redresses it. Closes elastic#45848
This was referenced Oct 1, 2019
albertzaharovits
added a commit
that referenced
this pull request
Oct 1, 2019
Due to a regression bug the metadata Active Directory realm setting is ignored (it works correctly for the LDAP realm type). This commit redresses it. Closes #45848
albertzaharovits
added a commit
that referenced
this pull request
Oct 1, 2019
Due to a regression bug the metadata Active Directory realm setting is ignored (it works correctly for the LDAP realm type). This commit redresses it. Closes #45848
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Oct 2, 2019
The changes introduced in elastic#47179 made it so that we could try to build an SSLContext with verification mode set to None, which is not allowed in FIPS 140 JVMs. This commit address that
jkakavas
added a commit
that referenced
this pull request
Oct 3, 2019
The changes introduced in #47179 made it so that we could try to build an SSLContext with verification mode set to None, which is not allowed in FIPS 140 JVMs. This commit address that
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Oct 3, 2019
The changes introduced in elastic#47179 made it so that we could try to build an SSLContext with verification mode set to None, which is not allowed in FIPS 140 JVMs. This commit address that
jkakavas
added a commit
that referenced
this pull request
Oct 3, 2019
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this pull request
Oct 12, 2019
The changes introduced in elastic#47179 made it so that we could try to build an SSLContext with verification mode set to None, which is not allowed in FIPS 140 JVMs. This commit address that
jkakavas
added a commit
that referenced
this pull request
Oct 12, 2019
39 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to a regression bug the
metadataActive Directory realm setting is ignored (it works correctly for the LDAP realm type). This commit redresses it.Closes #45848