ldapsearch -Y PLAIN -U swimonowar -W -b dc=myproject,dc=net -v -d 1
ldap_initialize( )
ldap_create
Enter LDAP Password:
ldap_sasl_interactive_bind_s: user selected: PLAIN
ldap_int_sasl_bind: PLAIN
ldap_new_connection 1 1 0
ldap_int_open_connection
ldap_connect_to_host: TCP localhost:389
ldap_new
anyone can clear to me about this line
To work, passwords for accounts will form OpenLDAP sasl) (account @ realm.
These two parameters, account, and the kingdom shall be forwarded to saslauthd
uses them in its LDAP filter to find the account in question.
On Jul 20, 2010, at 12:58 AM, Dan White
after the line executed
ldapsearch -Y PLAIN -U oshim -W -b dc=myproject,dc=net
Enter LDAP Password:
ldap_sasl_interactive_bind_s: Unknown authentication method (-6)
On Jul 20, 2010, at 12:58 AM, Dan White wrote:
> On 19/07/10 23:59 +0600, OSHIM wrote:
>> test:~/lsc/etc# ldapsearch -U oshim -W
Hi everyone.
I am writting a small LDAP client. I am just learning LDAP.
I need to provide LDAP over SSL.
I assume that when I use the ldap_start_tls_s() function that there is a public
key that is passed to my client.
How do I find out where this cert is stored on the client machine?
I trie
I suspect that once it has expired, it can't be used (it fails auth as it has
expired - and can't be used to auth even to change password)
For that reason, I have password expiration warning set to a few seconds less
than the password expiration time - although, as it returns '0' for the last 24
I am having problems with access control in slapd.conf.
If I leave all access control commented in slapd.conf, the ssh user can login
and id works.
But if the users password expires though the use of the ppolicy directives,
they are
prompted to change the password but cannot due to an Insuffic
On 19/07/10 23:59 +0600, OSHIM wrote:
test:~/lsc/etc# ldapsearch -U oshim -W -b dc=myproject,dc=net
Enter LDAP Password:
SASL/DIGEST-MD5 authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
You either need:
mech_list: PLAIN LOGIN
in your /usr/lib/sasl/slapd.conf
or
test:~/lsc/etc# ldapsearch -U oshim -W -b dc=myproject,dc=net
Enter LDAP Password:
SASL/DIGEST-MD5 authentication started
ldap_sasl_interactive_bind_s: Invalid credentials (49)
On Jul 19, 2010, at 9:57 PM, Dan White wrote:
> On 19/07/10 21:18 +0600, OSHIM wrote:
>> i have configured saslauthd w
I have added a new user with the pass {sasl}os...@myproject.net then i checked
it Apache Directory Studio it shows SASL hashed password. When I checked show
details then it shows me {sasl}os...@myproject.net.
but if i run ldapsearch -x -D "cn=oshim,dc=myproject,dc=net" -W -b
dc=myproject,dc=net
On 19/07/10 18:37 +0200, Jonathan Clarke wrote:
Le 19/07/2010 18:07, OSHIM a écrit :
I have added into /etc/ldap/slapd.conf
sasl-host localhost
sasl-secprops none
and also have created usr/lib/sasl2/slapd.conf and have added following
two lines
pwcheck_method: saslauthd
saslauthd_path: / var /
Le 19/07/2010 17:19, Gianluigi Nigro a écrit :
Hi,
on an empty and clean database (running for the first time) I get the error:
Jul 19 17:14:54 centostest slapd[27698]: @(#) $OpenLDAP: slapd 2.4.21
(Jul 19 2010 15:47:56) $
r...@centostest.passepartout.local:/opt/openldap-2.4.21/servers/slapd
J
Le 19/07/2010 18:07, OSHIM a écrit :
I have added into /etc/ldap/slapd.conf
sasl-host localhost
sasl-secprops none
and also have created usr/lib/sasl2/slapd.conf and have added following
two lines
pwcheck_method: saslauthd
saslauthd_path: / var / run / saslauthd / mux
With this configuration,
I have added into /etc/ldap/slapd.conf
sasl-host localhost
sasl-secprops none
and also have created usr/lib/sasl2/slapd.conf and have added following two
lines
pwcheck_method: saslauthd
saslauthd_path: / var / run / saslauthd / mux
On Jul 19, 2010, at 9:57 PM, Dan White wrote:
> On 19/07/
On 19/07/10 21:18 +0600, OSHIM wrote:
i have configured saslauthd with openldap to authenticate MS AD
when I run testsaslauthd -u swioshim -p Test2010 then i got 0: OK "Success."
(swioshim is my MS AD user and Test2010 password coming from MS AD)
but when i run
ldapsearch -x -D "cn=swioshim,dc
i have configured saslauthd with openldap to authenticate MS AD
when I run testsaslauthd -u swioshim -p Test2010 then i got 0: OK "Success."
(swioshim is my MS AD user and Test2010 password coming from MS AD)
but when i run
ldapsearch -x -D "cn=swioshim,dc=myproject,dc=com" -W -b dc=myproject,dc
Hi,
on an empty and clean database (running for the first time) I get the
error:
Jul 19 17:14:54 centostest slapd[27698]: @(#) $OpenLDAP: slapd 2.4.21
(Jul 19 2010 15:47:56) $
r...@centostest.passepartout.local:/opt/openldap-2.4.21/servers/slapd
Jul 19 17:14:55 centostest slapd[27699]: bdb_monit
Le 19/07/2010 12:45, OSHIM a écrit :
anyone can help me out
test:~# testsaslauthd -u swioshim -p Test2010
0: NO "authentication failed"
why authentication failed?
saslauthd usually logs to the syslog facility "auth". Check your
/var/log/auth.log (or similar, depending on your OS).
Jonathan
anyone can help me out
test:~# testsaslauthd -u swioshim -p Test2010
0: NO "authentication failed"
why authentication failed?
On Jul 19, 2010, at 12:57 AM, Dan White wrote:
> On 18/07/10 23:52 +0600, OSHIM wrote:
>> What we want to achieve is user using services like OpenVPN, webproxy,
>> emai
Hi Frederik!
Could you try a commit; after each SQL statement?
Best Regards
2010/7/19 Frederik Bosch
> Hello,
>
> With BackSQL I am trying to make my SQL data available for LDAP purposes.
> Setup went OK, server starts and my data is available. I have one problem.
> Modifications in the SQL da
Hello,
With BackSQL I am trying to make my SQL data available for LDAP
purposes. Setup went OK, server starts and my data is available. I have
one problem. Modifications in the SQL data do not seem to be executed
until I restart slapd. As if the SQL data is cached.
My setup uses openldap_2.4
20 matches
Mail list logo
