Re: [translate-pootle] Fwd: LDAPS

2010-05-19 Thread Ľuboš Katrinec
Ok, after some configuring and troubleshooting I've got it to work :-). Anyway, I've got another smaller issue. In localsettings.py there is a variable: AUTH_LDAP_FIELDS = { 'dn':'uid', #'first_name':'', 'last_name':'sn', 'email':'mail' } As you can see,

Re: [translate-pootle] Fwd: LDAPS

2010-05-19 Thread F Wolff
Op Wo, 2010-05-19 om 13:10 +0200 skryf Ľuboš Katrinec: Ok, after some configuring and troubleshooting I've got it to work :-). Great! Say if there is any advice for future users that we can document. Anyway, I've got another smaller issue. In localsettings.py there is a variable:

Re: [translate-pootle] Fwd: LDAPS

2010-05-19 Thread Ľuboš Katrinec
Op Wo, 2010-05-19 om 13:10 +0200 skryf Ľuboš Katrinec: Ok, after some configuring and troubleshooting I've got it to work :-). Great! Say if there is any advice for future users that we can document. All the configuration had to be set on LDAP server and client side: 1. First, I had to

Re: [translate-pootle] Fwd: LDAPS

2010-05-15 Thread Ľuboš Katrinec
What is the output of this command? python -c import ldap; print ldap.SASL_AVAIL; print ldap.TLS_AVAIL 1 1 This is ok, isn't it? I will try to try get LDAP over SSL to work with another client to find out if the problem is related with LDAP/SSL settings or in Pootle. Thanks so far, Lubos

Re: [translate-pootle] Fwd: LDAPS

2010-05-14 Thread F Wolff
Op Vr, 2010-05-14 om 16:35 +0200 skryf Ľuboš Katrinec: Hello Friedel, AUTH_LDAP_SERVER = 'ldaps://localhost:389' I've got {'info': 'A TLS packet with unexpected length was received.', 'desc': Can't contact LDAP server} Without s in the url: AUTH_LDAP_SERVER = 'ldap://localhost:389'