case of forcePasswordDefaultHash

forcePasswordDefaultHash is compared to "true" instead of "TRUE" in functions.inc in change_password.

(from redmine: issue id 2351, created on 2013-04-30, closed on 2013-05-08)

• Changesets:
  • Revision 2e6e9509 by Côme Chilliet on 2013-05-03T08:54:19.000Z:

Fixes: #2351 case of boolean configs

• Custom Fields:
  • Bug in version: 1.0.5
• Uploads:
  • 0001-Fixes-2351-case-of-boolean-configs.patch

The case was also wrong on some much more important feature such as ldapTLS. Please check that the following features are working:

• Setup option LDAP TLS
• Configfile option LDAP follow referral (with value "TRUE" or "FALSE")
• Config option force password hash

Maybe it should also be added to the documentation of migration 1.0.4->1.0.5 than TRUE and FALSE value should now be uppercase in fd.conf.

(from redmine: written on 2013-05-03)

By Côme Chilliet on 2017-09-02T14:58:54 (imported from GitLab)

Hello,

• Setup option LDAP TLS - it's ok (when start_tls is correctly configured). During setup fd automatically add ldapTLS="TRUE" in fd.conf. We can do that also manually, adding ldapTLS="TRUE" in location section of fd.conf

• Configfile option LDAP follow referral (with value "TRUE" or "FALSE") - I cannot configure to test it

• Config option force password hash - it's ok

(from redmine: written on 2013-05-07)

By gdivito on 2017-09-02T14:58:54 (imported from GitLab)

Close issue

(from redmine: written on 2013-05-08)

By bmortier on 2017-09-02T14:58:55 (imported from GitLab)

closed

By bmortier on 2017-09-02T14:58:55 (imported from GitLab)

added Fixed fusiondirectory-core and removed Bugs labels

By bmortier on 2019-01-11T20:48:48 (imported from GitLab)