Implement LDAP credentials validation via HTTP API#14661
Open
lukebakken wants to merge 1 commit intorabbitmq:mainfrom
Open
Implement LDAP credentials validation via HTTP API#14661lukebakken wants to merge 1 commit intorabbitmq:mainfrom
lukebakken wants to merge 1 commit intorabbitmq:mainfrom
Conversation
lukebakken
force-pushed
the
lukebakken/ldap-validation-api-plugin
branch
from
88b03fa to
c25f38f
Compare
lukebakken
force-pushed
the
lukebakken/ldap-validation-api-plugin
branch
from
9df993f to
3acb159
Compare
lukebakken
force-pushed
the
lukebakken/ldap-validation-api-plugin
branch
from
3acb159 to
c70b579
Compare
Collaborator
|
Looks like the move of LDAP helpers into Adding |
lukebakken
force-pushed
the
lukebakken/ldap-validation-api-plugin
branch
2 times, most recently
from
354172e to
668ed4d
Compare
lukebakken
force-pushed
the
lukebakken/ldap-validation-api-plugin
branch
3 times, most recently
from
772312c to
8ffbddd
Compare
See discussion rabbitmq#14244 Follow-up to rabbitmq#14414 Cherry-picked from 9a4cb9c and then modified to move validation API endpoint to a separate plugin, `rabbitmq_auth_backend_ldap_management`. These changes will allow a user to make an HTTP API request to... ``` /api/ldap/validate/simple-bind ``` ...with an appropriate JSON body, and the plugin will attempt a connection to the specified LDAP server using the provided credentials. This allows validation that a connection can be made to an LDAP server from a RabbitMQ cluster environment.
lukebakken
force-pushed
the
lukebakken/ldap-validation-api-plugin
branch
from
8ffbddd to
2ad9446
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
See discussion #14244
Follow-up to #14414
Cherry-picked from 9a4cb9c and then modified to move validation API endpoint to a separate plugin,
rabbitmq_auth_backend_ldap_management.These changes will allow a user to make an HTTP API request to...
...with an appropriate JSON body, and the plugin will attempt a connection to the specified LDAP server using the provided credentials. This allows validation that a connection can be made to an LDAP server from a RabbitMQ cluster environment.