-
Notifications
You must be signed in to change notification settings - Fork 324
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
Added ldap_user_federation attribute trust_email #267
Added ldap_user_federation attribute trust_email #267
Conversation
That makes sense, thanks for the explanation. I went ahead and updated CI to pass a Everything else LGTM. |
08be1e6
to
360ca71
Compare
I added a utility function that extracts the Keycloak major version from the new environment variable KEYCLOAK_VERSION. The test sets the first and second value for "trustEmail" to false if the Keycloak version is <8. This should work as the variable is fetched using The test still fails though and I cannot figure out why. In the output I see changes in I could not figure out how to do single step debugging into the test (IntellIJ just stopped) or where exactly this output comes from. So you need to help a bit here. |
secondTrustEmail = !firstTrustEmail | ||
} else { | ||
firstTrustEmail = false | ||
secondTrustEmail = false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks like this is still failing.
It might be best to remove the trustEmail
stuff from this test and make a separate test specifically for testing this attribute. Then we can skip that test if the version of Keycloak doesn't support it.
360ca71
to
c889abc
Compare
I rebased the patch to the current master branch. |
Sorry for just now getting back to this @lathspell. Since we don't need to look at the |
c889abc
to
705150f
Compare
705150f
to
340ec21
Compare
I rebased the patch. Is it ok to merge now? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thanks for the PR!
Something strange happened with Pull Request 251, one of my git-rebase actions seems to have closed it?
The problem with Keycloak 7.0.1 is that the GUI does not support the "trust_email" attribute in this version. It is not in the Admin Webinterface nor in the representation that is reported back in the API.
How do you usually cope with such attributes? Is there a good way to throw an error depending on the version? If you can give me an example, I could try to enhance the patch.
original Text from Pull Request 251:
fixes #234
It's a simple boolean value, I copy & paste fixed it whereever I found ValidatePasswordPolicy/validate_password_policy.
Verified that it can in fact turn the setting on and off in Keycloak 8.0.1.