View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0033444 | mantisbt | authentication | public | 2023-12-15 18:13 | 2024-01-08 16:17 |
Reporter | phruby | Assigned To | dregad | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Summary | 0033444: LDAPS not working | ||||
Description | I am using the latest version of MantisBT 2.25.5. $g_login_method = LDAP; I'm getting this error: It won't bind to the corporate server. I have company certificates that are installed on the server. Do these certs need to go somewhere on the site? They don't think they are setup correctly. I've tried it with $g_ldap_use_starttls = ON; but no change. | ||||
Additional Information | Related forum post https://www.mantisbt.org/forums/viewtopic.php?t=28211 | ||||
Tags | No tags attached. | ||||
phruby, If you use starttls, then your bind URL should be plain ldap:// on port 389 (i.e. not ldaps://). And indeed your SSL certificates need to be configured on the server. This is not a bug or feature request for MantisBT (you are asking for help on how to configure the system). I am therefore resolving this issue as "no change required". Please use the forums to get support on customizing and using MantisBT (refer to https://www.mantisbt.org/support.php for links and further details). |
|
The SSL certificates are configured correctly on the server. Our IT says to use $g_ldap_server = 'ldaps://us.bank-dns.com:636'; Why is it using administrator? I want it to use my AD service account as listed in $g_ldap_bind_dn $g_login_method = LDAP; No one has a solution on the forums and they get very little traffic. I'll post this there too. |
|
I understand this could be confusing, but this is not the actual LDAP connection to authenticate the user, only a "sanity check" that is performed in the login page to ensure that you have changed the default administrator account's password which is assigned when installing MantisBT. Subsequent LDAP calls will use the configured $g_ldap_bind_dn. You can disable this behavior either by setting Assuming you're still facing the same error as reported in your original post:
Please note that what you see in the MantisBT log is the error that is triggered by PHP's ldap_bind() function, as returned by ldap_error() - we are just reporting it back and have no control over what is happening in or beyond PHP's LDAP extension. You can test and confirm this by running a simple script like
Therefore, this is not a MantisBT bug, but a problem with your system's configuration and as mentioned previously this is not the right channel to discuss configuration issues. I would suggest, if possible, to test if the connection works with a plain LDAP connection (i.e. without SSL) over port 389. If that works then you're most likely facing an issue with certificates configuration. |
|
@phruby to help troubleshoot your problem, you may want to increase the LDAP debug level (e.g. set to LDAP_DEBUG_ANY). Adapting the test script I posted earlier:
On an incorrectly configured Windows PC at work, this gives |
|