Repository navigation
Enable MapUserProvider storing username with the letter case signific… - #13183
Conversation
There was a problem hiding this comment.
@vramik Thanks for getting into this. I've reviewed the whole thing and I must say I find it a bit confusing for the user provider to check a property set in the realm storage config. I say this because the storages themselves (JPA, hotrod, etc) never actually use this property and it feels like this switch has been put in the wrong place.
Perhaps I'm failing to see how this is supposed to work with realm-specific stores, but I have to say that this switch is really confusing to me.
9c4bfeb to
a60c0dc
Compare
a60c0dc to
31f86e6
Compare
You're right it was misplaced at that stage of the draft PR. The setting now is taken from realm attribute (if the realm is available) upon creation of user provider. Default setting is The implementation follows #10198 (comment) and also incorporates #10198 (comment) and should be ready for a review |
There was a problem hiding this comment.
Thank you @vramik, this PR is going in the right direction.
Please see a few inline comments. After addressing the two main comments re the session attribute and lowercase variant of the username, it should be good to be merged
f922672 to
0c20e31
Compare
There was a problem hiding this comment.
Would it be possible to add integration tests which scenarios where
- realm with case sensitivity search is (a) enabled, (b) disabled
- create a user
- search for the user by (a) uppercase, (b) original letter case, (c) lowercase username
- switch the case sensitivity flag to the other state
- search as previously
31472f6 to
b7eccc6
Compare
0a007d5 to
12fe932
Compare
12fe932 to
90feeb2
Compare
90feeb2 to
0dd7db9
Compare
|
undertow-map-jpa, group1 failed due to #14270 |
…ance
Closes #10245