You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on my previous issue, which was closed too sooned by the bot.
I found the "problem" but as I can't make a PR, I propose these differents solution to helps the next adminsys (and avoid him to create another issue) that will try to configure LDAPS and thinking everything is correctly configured but no.
Not working LDAPS configuration
Working LDAPS configuration
Why do we have to specify the protocol ldaps:// in the server field when we are already setting port field with 636.
Then why we don't need to specify ldap:// when it is by default the port 389.
I propose different fixes:
Add a condition in the code that checks if the user configures port 636 but did not write ldaps:// in the server field, then a detailed error log informs the user.
Change the field description Server to something like this
Edit LDAP configuration interface:
replace the port field with an LDAP / LDAPS selection button
(depending on the choice, it will pre-fill the server field with ldaps:// and port 636 or the default ldap and 389)
Relevant log output
No response
Page URL
No response
Steps To reproduce
No response
Your GLPI setup information
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
This issue has been closed as we only track bugs here.
You can open a topic to discuss with community about this enhancement on suggestion website.
You can also contact GLPI editor team directly if you are willing to sponsor this feature.
Code of Conduct
Is there an existing issue for this?
Version
10.0.14
Bug description
Based on my previous issue, which was closed too sooned by the bot.
I found the "problem" but as I can't make a PR, I propose these differents solution to helps the next adminsys (and avoid him to create another issue) that will try to configure LDAPS and thinking everything is correctly configured but no.
Why do we have to specify the protocol
ldaps://
in theserver
field when we are already settingport
field with636
.Then why we don't need to specify
ldap://
when it is by default the port 389.I propose different fixes:
Add a condition in the code that checks if the user configures port 636 but did not write ldaps:// in the server field, then a detailed error log informs the user.
Change the field description Server to something like this
ldaps://
and port636
or the default ldap and 389)Relevant log output
No response
Page URL
No response
Steps To reproduce
No response
Your GLPI setup information
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: