Remove password checks in REST API calls #14386
Merged
Conversation
This file contains 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
…er JAAS authentication if Enterprise is used and Hazelcast Security is enabled.
kwart
force-pushed
the
rest-jaas-security
branch
from
bc8cb02
to
aec2e8e
Compare
emre-aydin
approved these changes
Jan 17, 2019
tkountis
approved these changes
Jan 17, 2019
|
Thanks for reviews guys! Merging this and I'll rebase the other REST PR afterwards. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR removes password checks in REST API calls - only group name checks remain.
If the Hazelcast Security is enabled (on Enterprise members) then JAAS authentication is used to verify the request against member login module stack.
The commit aligns the password checking behavior to other parts of Hazelcast (members & clients authentication).