Tracker log
An overview of recent activity in the tracker.
- Siegfried Koch added a new response to »ldapconfig use_ssl=1 ignored in LDAPServer_Configuration«:
-
Thanks Jean-Paul,
I studied the modified sources and did a short testing ...
Works fine for me :-)
SiegfriedAdded 1340 day(s) ago.
- Jean-Paul Ladage added a new response to »ldapconfig use_ssl=1 ignored in LDAPServer_Configuration«:
-
Hi Siegfreid,
I added the proposed options and created a new tag 0.2
Could you please try that and see if it works? I set the default to NOT use SSL btw.
Jean-PaulIssue state: unconfirmed → resolved.
Responsible manager: (UNASSIGNED) → jladage.
Added 1343 day(s) ago. - New issue »ldapconfig use_ssl=1 ignored in LDAPServer_Configuration« added by Siegfried Koch
-
I'm Using Plone 3. with LDAPMultipluguins 2.8 and LDAPUserfolder 1.5
and managed to setup an appropriate ldapconfig.py file after applying the patches to LDAPMultiPlugins
I decided to chekc out ldapconfig beacuse I have to "Add PloneSite" for appr. 120 diferent sites with same LDAP-authentication-sources; we use LDAPS
Even though I specified use_sll = 1 in ldapconfig.py the procedure adding the LDAP-Servers selects LDAP and and Port 389
Looking into the source of ../ldapconfig/Extensions/install.py I could figure out that in calling
for ldap_host in ldaphosts:
ldapFolder.manage_addServer(host=ldap_host,
conn_timeout=ldapConfig['LDAP_CONN_TIMEOUT'],
op_timeout=ldapConfig['LDAP_OP_TIMEOUT'])
#
at lines 103++ the attributes use_ssl and port are not provided.
I did a tiny modification -- just to chekc the impact --- and it worked :-)))
for ldap_host in ldaphosts:
ldapFolder.manage_addServer(host=ldap_host,
use_ssl = 1, ###### FOR TEsting ONLY
port=636, ###### FOR TESTING ONLY
conn_timeout=ldapConfig['LDAP_CONN_TIMEOUT'],
op_timeout=ldapConfig['LDAP_OP_TIMEOUT'])
#
Questions:
I' highy appreciate if you might check, what I've figured out and give an info whether support for the attributes "use_ssl" and "port" might get provided in future releases.
And it would be great to get assistance in moving th "dirty fix" described above into a quality-fix, useful for others to.
Many thanks
Siegfried
PS: Guess my contribution is closer to Issue Type Feature than Bug or PatchAdded 1343 day(s) ago.
- Maurits van Rees added a new response to »Which version of LDAPMultiPlugins should be used for patching?«:
-
Fixed in revision 35399.
Issue state: open → resolved.
Added 1862 day(s) ago. - Maurits van Rees added a new response to »Which version of LDAPMultiPlugins should be used for patching?«:
-
Issue state: unconfirmed → open.
Added 1862 day(s) ago. - New issue »Which version of LDAPMultiPlugins should be used for patching?« added by Maurits van Rees
-
ldapconfig's README.txt mentions it uses LDAPMultiPlugins 1.4 but PLUGINS.txt mentions to use LDAPMultiPlugins 1.2
Actually, it should be 1.4 from subversion trunk.Added 1862 day(s) ago.
