Skip to content

Clarification on search user #9307

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

Merged
merged 2 commits into from
May 28, 2018
Merged

Clarification on search user #9307

merged 2 commits into from
May 28, 2018

Conversation

brooksvb
Copy link
Contributor

I had issues with configuration because I misunderstood the configuration for the user provider. I didn't realize that the configured user was actually a static one only used for retrieving information.

I also added a clarification for the case that you are getting information anonymously, which was what my situation required.

These changes are relevant for Symfony 2.8+ (2.8 being the oldest maintained version I checked)

Also, I added a note on keeping the password out of VC by using a parameter, but in Symfony 4 this should be an environment variable instead. I'm not sure how I'm supposed to propose the change for this slight difference once hitting that version.

I had issues with configuration because I misunderstood the configuration for the user provider. I didn't realize that the configured user was actually a static one only used for retrieving information. 

I also added a clarification for the case that you are getting information anonymously, which was what my situation required.
@xabbuh xabbuh added the Ldap label Apr 20, 2018
@xabbuh xabbuh added this to the 2.8 milestone Apr 20, 2018
Copy link
Member

@xabbuh xabbuh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Member

@javiereguiluz javiereguiluz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for this contribution but I'd like to ask some changes:

  1. We can remove this: "If you wish to keep your password out of version control, you may want to configure the password as a parameter." because we already explain that in other articles and we want to minimize repeated Symfony Docs contents to ease maintenance.

  2. I don't understand this phrase: "It's important to note that the user you configure for the user provider is only going to be retrieving data." and this other phrase: "It is a statically defined user and password. "

I wonder if we can reword this as follow:

.. tip::

    If your LDAP server allows you to retrieve information anonymously, you
    can leave the ``search_dn`` and ``search_password`` as ``null``.

@javiereguiluz javiereguiluz dismissed their stale review May 28, 2018 07:13

Comments are no longer relevant

@javiereguiluz
Copy link
Member

Thanks for helping us improve Symfony Docs and I'm sorry it took us so long to merge this.

@javiereguiluz javiereguiluz merged commit b7a2009 into symfony:2.8 May 28, 2018
javiereguiluz added a commit that referenced this pull request May 28, 2018
This PR was merged into the 2.8 branch.

Discussion
----------

Clarification on search user

I had issues with configuration because I misunderstood the configuration for the user provider. I didn't realize that the configured user was actually a static one only used for retrieving information.

I also added a clarification for the case that you are getting information anonymously, which was what my situation required.

These changes are relevant for Symfony 2.8+ (2.8 being the oldest maintained version I checked)

Also, I added a note on keeping the password out of VC by using a parameter, but in Symfony 4 this should be an environment variable instead. I'm not sure how I'm supposed to propose the change for this slight difference once hitting that version.

Commits
-------

b7a2009 Minor reword
f08eab2 Clarification on search user
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants