View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0028328 | mantisbt | authentication | public | 2021-04-19 12:41 | 2022-06-24 18:42 |
Reporter | martin.fernau | Assigned To | dregad | ||
Priority | normal | Severity | block | Reproducibility | have not tried |
Status | closed | Resolution | no change required | ||
OS | debian | OS Version | 9.13 | ||
Product Version | 2.25.0 | ||||
Summary | 0028328: After Upgrade I got "APPLICATION ERROR #1406" with ERROR_LDAP_UNABLE_TO_STARTTLS after login | ||||
Description | I found bug 0015361 which mentioned ERROR_LDAP_UNABLE_TO_STARTTLS. Unfortunately I don't know where to start or what to do to fix that.. With previous mantis 2.21.1 I was able to work with LDAP authentication since a long time. After upgrading to 2.25. my system stops to work Could anyone please point me to the right direction? In the meanwhile I need to rollback my installation | ||||
Tags | No tags attached. | ||||
This note might explain it. As a workaround adding the following line to config_inc.php might work |
|
Thank you - I found the problem. to: |
|
Really? I don't see any place in source code where LDAPS is used to check login_method. |
|
If I change it back to "LDAP" I get the mentioned error again (see attachment - but its German). I'm confused too |
|
@martin.fernau good to hear you fixed your problem. FYI, the standard way to connect securely with LDAP is with StartTLS, which is what Mantis now does by default ($g_ldap_use_starttls = ON). Usage of the |
|
Even more funny: |
|
What @atrol means, is that
or (insecure, not recommended)
or, the recommended method which requires your LDAP server to be properly configured to handle StartTLS (which is apparently not the case) |
|
In reply to 0028328:0065409
$g_login_method expects an integer value (for example, constant LDAP = 3). In PHP, an arbitrary string evaluates to 0, so with These legacy login methods really need to be removed, but that is another story (0022839) |
|
You did not provide any feedback since more than one year, so I assume you were able to fix your problem. I'll resolve this issue as "no change required". Feel free to reopen it at a later time and provide the requested information. |
|