Skip to content

LDAP Users import problem #544

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

Closed
jdanielcano opened this issue Apr 20, 2017 · 9 comments
Closed

LDAP Users import problem #544

jdanielcano opened this issue Apr 20, 2017 · 9 comments

Comments

@jdanielcano
Copy link

Hello there,

First of all, thanks for the great job you are doing with this tool, it is great and it has many and useful features.
I am trying to install the sysPass in the following way:

  • Docker containers running in a Debian Jessie 8.7.
  • SysPass application running in a Docker container using the SysPass version 2.1.2.17031401.
  • The database MySQL 5.5. I use the Hosting option cause our database server is in a different machine, so we connect with a dedicated user into the database.

The problem:

  • Every time we try to import the users from LDAP I got this output:
LDAP users import finished
Imported users : 0/200
Errors : 0 

I checked the logs and there is no errors, even in the database logs there is anything weird or error. When I try to list the users in the LDAP configuration, I can retrieve all the users from the LDAP and I can "navigate" or list all of them, but the import is not working.

I am doing something wrong?

Thanks a lot in advance.
Cheers,
Daniel.

@nuxsmin
Copy link
Owner

nuxsmin commented Apr 20, 2017

Hello Daniel,

I'm very glad that you found it useful ;)

Regarding your issue, it could be related to the LDAP Login Attribute which is used to get the users login when performing the import, so if this attribute is not set in the LDAP user data, the user won't be imported.

Cheers!

@jdanielcano
Copy link
Author

Hello!

Thanks for the quick answer!

Actually the login attribute exist, in our case the UID, and I am selecting that option during the import process...

Thanks again!
Cheers,
Daniel

@nuxsmin
Copy link
Owner

nuxsmin commented Apr 20, 2017

I forgot to mention that the username and login shouldn't be blank so if the user login is got, the username could be the cause.

Cheers

@nuxsmin
Copy link
Owner

nuxsmin commented Apr 20, 2017

Sorry...and the username is got either from displayname or fullname attributes

@jdanielcano
Copy link
Author

Ok, then that is the cause, for the user name we use the CN and not the displayname or fullname.
Probably this could be another feature as it is now for the login? I mean, to be able to chose from which attribute the username could be taken?

Thanks a lot!
Cheers,
Daniel

@jdanielcano
Copy link
Author

Hi again,

I add the attribute cn in the code and it is working, if you agree, I will make a pull request to add this attribute in the 2 files needed to add the attribute as a possibility to be used as username.

Thanks again.
Cheers,
Daniel

@nuxsmin
Copy link
Owner

nuxsmin commented Apr 20, 2017

Nice, please send me the pull request.

Thanks!

Cheers

nuxsmin added a commit that referenced this issue Apr 20, 2017
… to get from the LDAP server. Solves #544. Thanks to @jdanielcano for the feedback

* [MOD] Updated translations.
@nuxsmin
Copy link
Owner

nuxsmin commented Apr 20, 2017

Hi @jdanielcano

I've just implemented the code that allows to select the name attribute for importing from LDAP :)

Cheers

@nuxsmin nuxsmin closed this as completed Apr 20, 2017
@jdanielcano
Copy link
Author

jdanielcano commented Apr 20, 2017 via email

nuxsmin added a commit that referenced this issue Apr 26, 2017
… to get from the LDAP server. Solves #544. Thanks to @jdanielcano for the feedback

* [MOD] Updated translations.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants