Skip to content

Conversation

@vitormazzi
Copy link

This option allows the authentication of users with multiple unknown
distinguished name (dn) formats, provided that there is at least one
user whose dn is known and has the permissions to search for other
users.

This option allows the authentication of users with multiple unknown
distinguished name (dn) formats, provided that there is at least one
user whose dn is known and has the permissions to search for other
users.
@sjkingo
Copy link
Owner

sjkingo commented Aug 31, 2016

Thanks for your PR. Could you explain a little how this is different to method 2 (search and bind), except with a custom filter?

@sjkingo
Copy link
Owner

sjkingo commented Aug 31, 2016

It would be awesome to merge this into the code as the search and bind method (issue #2) as that has been a long-standing feature I've wanted to implement.

@vitormazzi
Copy link
Author

I don't have a lot of ldap knowledge, so I'm not really sure about the differences. That is the main reason I proposed this code as a third authentication method.

The only incompatible point I see at this moment is that the search step in search and bind could be anonymous (is that right?), and in my code it requires a valid password. Do you see anything else?

Replacing references to `EntryBase.entry_get_dn()` with
`EntryBase.entry_dn`, as this method does not exist anymore.

Using a specific version of ldap3 from now on, as this api change
caught us off guard.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants