passwordProposalHook
passwordProposalHook
In Gosa 2.7 there is an option called "passwordProposalHook" in gosa.conf.
From doc:
passwordProposalHook command
The passwordProposalHook can be used to let GOsa generate password proposals for you. Whenever you change a password, you can then decide whether to use the proposal or to manually specify a password.
/usr/bin/apg -n1
It would be nice if FD could also propose passwords on new user creation. In our case receptionists should create new WiFi users via FD and i don't want them to have to invent a password every time. It could be build-into FD or via an external hook. For example call a console command like in the gosa example above, or call a URL to get the password in an answer.
(from redmine: issue id 4001, created on 2015-08-12, closed on 2016-01-04)
- Relations:
- copied_to #4280
- Changesets:
- Revision 46069295 by Côme Chilliet on 2015-11-05T11:28:20.000Z:
Fixes #4001 Added a random string modifier- Revision f20b783c by Côme Chilliet on 2015-11-05T11:29:26.000Z:
Fixes #4001 Added a random string modifier- Revision 205235ca by Côme Chilliet on 2016-01-04T02:29:26.000Z:
Fixes #4001 fixed mistake in random modifier handling- Revision 182b0774 by Côme Chilliet on 2016-01-04T02:30:07.000Z:
Fixes #4001 fixed mistake in random modifier handling- Custom Fields:
- Bug in version: 1.0.8.9
- Uploads:
Activity
Added a random string modifier, so you should be able to use something like: @%r[6,10,b]|%@ First parameter is minimum length, second one is maximum length, third one must be either l for letters, d for digit or b for both. Default is both. Default length is 8. If only one parameter it’s considered to be fixed length. If you want only lowercase or uppercase just use the l or u modifier after the r one: @%r[6,10,l]u|%@ I could not test it because my FD login is broken by CAS tests right now…
(from redmine: written on 2015-11-05)
By Côme Chilliet on 2017-09-02T15:22:17 (imported from GitLab)
Upgraded to 1.0.9.1-fixes with a lot of help from k1412 (thank you). %r[6,10,b]|% seems to do nothing until now. So i guess i have to wait for 1.0.9.2 to be able to test it ?
Another thought that came to my mind:
If i put "%r[6,10,b]|%" in "Mot de passe" in my template it automatically puts it also into "Mot de passe (de nouveau)". So when i create a new user using that template (when the random string works), won't it create two different random strings ? One for password and one for password confirmation ? And thus refuse to save the password because the two do not match ?
Serge
(from redmine: written on 2015-12-22)
By Foxi352 on 2017-09-02T15:22:17 (imported from GitLab)
I see PHP errors too. I can maybe help.
My template look so:
cn=template_cn,ou=templates,ou=people objectClass fdTemplate fdTemplateField objectClass:inetOrgPerson fdTemplateField objectClass:organizationalPerson fdTemplateField objectClass:person fdTemplateField userPassword:{SSHA}uCu9olRBXYRamsOw0BJ6ApA8V+AHD0aZ| %r[6,10,b]|% cn template_cnWhen I use my template to create an user, I have these PHP errors.
Cheers.
(from redmine: written on 2015-12-22)
By Jonathan Swaelens on 2017-09-02T15:22:18 (imported from GitLab)
I fixed these errors, please test again.
Another thought that came to my mind:
If i put "%r[6,10,b]|%" in "Mot de passe" in my template it automatically puts it also into "Mot de passe (de nouveau)". So when i create a new user using that template (when the random string works), won't it create two different random strings ? One for password and one for password confirmation ? And thus refuse to save the password because the two do not match ?
I don’t think so, as you can see in Jonathan LDAP dump the mask is stored only once in the template, so I think we’ll be OK. Needs testing though.
(from redmine: written on 2016-01-04)
By Côme Chilliet on 2017-09-02T15:22:18 (imported from GitLab)
added Added user-manual labels
By bmortier on 2018-10-05T12:51:46 (imported from GitLab)
