Re: Issue 1933 in reviewboard: Getting new user details from LDAP are not using binded user account
Updates: Status: Fixed Comment #2 on issue 1933 by trowb...@gmail.com: Getting new user details from LDAP are not using binded user account http://code.google.com/p/reviewboard/issues/detail?id=1933 This has since been fixed. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard-issues+unsubscr...@googlegroups.com. To post to this group, send email to reviewboard-issues@googlegroups.com. Visit this group at http://groups.google.com/group/reviewboard-issues. For more options, visit https://groups.google.com/groups/opt_out.
Re: Issue 1933 in reviewboard: Getting new user details from LDAP are not using binded user account
Updates: Labels: Component-Accounts Comment #1 on issue 1933 by trowb...@gmail.com: Getting new user details from LDAP are not using binded user account http://code.google.com/p/reviewboard/issues/detail?id=1933 (No comment was entered for this change.) -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 1933 in reviewboard: Getting new user details from LDAP are not using binded user account
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 1933 by daChaac: Getting new user details from LDAP are not using binded user account http://code.google.com/p/reviewboard/issues/detail?id=1933 What version are you running? 1.5.1 What's the URL of the page containing the problem? N/A What steps will reproduce the problem? 1. Setup LDAP directory in a way that only uid and dn fields are primarily visible for anonymous users. Eg. other user details are hidden until user is authenticated. 2. Setup LDAP backend to authenticate against LDAP directory and look for uid=login. Do not use special account for initial bind. 3. Login with new user not previously on the system 4. New user does not have givenName nor sn set. What is the expected output? What do you see instead? givenName and sn set for new user. What operating system are you using? What browser? Linux; but not relevant to this issue. Please provide any additional information below. One fix for the issue would be to provide ldapo object from LDAPBackend::authenticate - LDAPBackend::get_or_create_user. And as user was previously binded in authenticate then ldapo.search_s would provide needed details in get_or_create_user. Another thing is that ldapo.search_s after binding might be also useful to allow updates from LDAP to local user database. Thou it might be a good idea to make this configurable. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-iss...@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
