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.
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
Add the capability for the LDAP and AD realms to bind using Kerberos credentials #41126
Add the capability for the LDAP and AD realms to bind using Kerberos credentials #41126
Changes from all commits
cd80858
42ff127
230bc87
33dbb09
d3be59f
20cbecd
e29cf26
7332792
26ae7da
955469e
b2b4963
841f394
eaa5965
e6eda93
d9e5293
23bfb73
0ee24b1
1119857
986ff5e
7a5dc4c
b6dba5d
6fbf757
460b8aa
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
can't these be moved to
x-pack/plugin/security/src/main/plugin-metadata/plugin-security.policy
?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.
No, as unboundid dependencies are in the
core
we need to have these here. Thank you.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.
I think these are a lot of obscure permissions we're granting for any plugin (that inherits
x-pack-plugin-core
). I worry especially about the maintainability. In this case I think we should move theunboundid
dependency over to the security plugin. I think it should not have been a dependecy inplugin-core
in the first place. The only imported class from that dependecy inplugin-core
is an enum,LdapSearchScope
, which I think we should emulate our own and use that inplugin-core
and adapt the APIs.What do you think?
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.
++ on moving the dependencies and getting the permissions in one place, though I see a TODO which I think is a non-trivial change and would require considerable thought as I am not much aware of what needs to be done here.
https://github.com/elastic/elasticsearch/blob/73bfdc4066be080dc4cad1f0521bf6ea14cded93/x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/XPackPlugin.java#L95..L124
I think I will pick this up later as a cleanup task. Thank you.