Syspass: AD Ldap : user disabled

[anburhce]

Hi Nuxsmin,

first of all: Thank you to all contributors for this great software .

i have implemented the syspass 1.2 on centos 7 and integrated with AD Ldap . when i try to login using AD user i am getting the below email to for "Account Activation " .

==

Your account activation is pending.
You will receive a confirmation email shortly.

--
sysPass - Systems Password Manager
http://172.30.0.245/syspass

==

But am not getting any confirmation mail later to enable the Account .

please help to solve the issue .

currently i am activating the account by login as admin and unselect "Disabled" option in user account .

[nuxsmin]

Hi @anburhce,

That email is sent when any LDAP user is added to sysPass, but it's only for information purposes, because that confirmation email would be sent by any sysPass admin when the account is fully configured.

sysPass won't send any confirmation email.

Kind regards

[nuxsmin]

In addition, that is so because sysPass doesn't know which profile or group the user belongs to.

[tumtumdev]

Hi Nuxsmin,

Is it possible to sync or import LDAP users into syspass?
Currently the default group is limited for every 'new' user.

I want to import the new users and assign the account directly to the correct profile and group, before they login. Is this possible with a script or this tool? This is one of the reasons it is hard to control the user rights with LDAP. (First login with the masterkey > Check the login and assign the profile/group > Change userpassword option in windows for first time login > Complete) or just Import/Sync > Assign Groups > Done

[anburhce]

thank you Ruben .

On Thu, Nov 17, 2016 at 12:50 PM, tumtumdev [email protected]
wrote:

Hi Nuxsmin,

Is it possible to sync or import LDAP users into syspass?
Currently the default group is limited for every 'new' user.

I want to import the new users and assign the account directly to the
correct profile and group, before they login. Is this possible with a
script or this tool? This is one of the reasons it is hard to control the
user rights with LDAP. (First login with the masterkey > Check the login
and assign the profile/group > Change userpassword option in windows for
first time login > Complete)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nuxsmin/sysPass/issues/337#issuecomment-261173820,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AWXgMZRFoyLbH3cevdY2C7-F0wbILTPlks5q_ABUgaJpZM4KxT4-
.

[nuxsmin]

Hi @tumtumdev

Actually not, but I'm implementing that feature for the next release.

[nuxsmin]

You're welcome @anburhce

[tumtumdev]

Thanks! It would also be awesome if the masterkey isnt required for a userlogin with ldap. With a lot users, it is hard to save it or to provide every 100~ days a new key.

[nuxsmin]

The new master key implementation will be seamless, that is, it will be required for first time the user logs in and whenever the key is changed. Afterwards, the only password required will be the user's one.

[tumtumdev]

Ok, nice, It will save a lot questions every ~100 days! Thank you

[nuxsmin]

Done in sysPass 2.0-beta