Joshua Van Horn wrote:
> Hi,
>
> I have compiled sasl-2.1.22 against openladp-2.3.39. After setting up
> the saslauthd.conf file, I was able to successfully authenticate against
> our SunONE LDAP server using testsaslatuhd. My issues arise when I
> start the cyrus-imapd program. I am able to l
Hi,
I'm also using saslauthd with ldap.
The only needed configuration of cyrus is
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN
You can remove all the other lines.
I then have in my saslauthd.conf file the following lines:
ldap_auth_method: custom
ldap_bind_dn:
ldap_bind_pw:
ldap_defau
Hi,
I have compiled sasl-2.1.22 against openladp-2.3.39. After setting up
the saslauthd.conf file, I was able to successfully authenticate against
our SunONE LDAP server using testsaslatuhd. My issues arise when I
start the cyrus-imapd program. I am able to login via Thunerbird/random
IMAP cli
Igor Brezac wrote:
ldap_filter: (&(ugentMailUid=%u%R)(ugentMailAccountStatus=enabled))
I used this and it works!
Thank you!
--
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Rudy Gevaert e-mail: [EMAIL PROTECTED]
Directie ICT, Afdeling I
On Wed, 10 May 2006, Rudy Gevaert wrote:
I forgot to add the following:
jura:/mail/mail1/etc# cat imapd.conf
admins: cyrus
allowanonymouslogin: no
altnamespace: yes
configdirectory: /mail/mail1/var/imap
defaultdomain: ugent.be
defaultpartiton: default
duplicatesuppression: 1
expunge_mode: dela
I forgot to add the following:
jura:/mail/mail1/etc# cat imapd.conf
admins: cyrus
allowanonymouslogin: no
altnamespace: yes
configdirectory: /mail/mail1/var/imap
defaultdomain: ugent.be
defaultpartiton: default
duplicatesuppression: 1
expunge_mode: delayed
hashimapspool: 1
mboxkey_db: skiplist
mb
On Wed, 10 May 2006, Rudy Gevaert wrote:
Hello,
I have configured sasl 2.1.19 (the one that is in Debian) to use LDAP. This
works as my gives an OK:
jura:/# testsaslauthd -u [EMAIL PROTECTED] -p pass
0: OK "Success."
saslauthd[4147] :do_auth : auth success:
[EMAIL PROTECTED] [serv
Hello,
I have configured sasl 2.1.19 (the one that is in Debian) to use LDAP.
This works as my gives an OK:
jura:/# testsaslauthd -u [EMAIL PROTECTED] -p pass
0: OK "Success."
saslauthd[4147] :do_auth : auth success:
[EMAIL PROTECTED] [service=imap] [realm=] [mech=ldap]
saslauthd[41
Re: Cyrus IMAP / SASL / LDAP virtual domain authentication
> use ldap_filter: %u%R
-Igor
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
On Tue, 18 Apr 2006, [EMAIL PROTECTED] wrote:
Hello,
I'm trying to set up Cyrus IMAP for virtual domains and authenticating
users in LDAP.
I have the basic configuration working but I have a problem that for
"[EMAIL PROTECTED]" the authentication sent to LDAP is just for "myuser".
I believe t
hi john,
try adding
ldap_default_realm: domain.tld
ldap_realm: domain.tld
to your saslauthd.conf & restart saslauthd
cheers
charles
On Tue, 2006-04-18 at 05:12 -0400, [EMAIL PROTECTED] wrote:
> Hello,
>
> I'm trying to set up Cyrus IMAP for virtual domains and authenticating
> users in LDA
Hello,
I'm trying to set up Cyrus IMAP for virtual domains and authenticating
users in LDAP.
I have the basic configuration working but I have a problem that for
"[EMAIL PROTECTED]" the authentication sent to LDAP is just for "myuser".
I believe this is down to SASL defaulting the ldap filter to
Hi!
I have a (dirty) testinstall on SuSE 9.2. I changed SASL with v. 2.1.21
for ldapdb. Works so far.
I installed a AIX server with OpenLDAP, SASL und IMAPd und copied the
conf. and LDAP data from SuSE server.
OpenLDAP works as on SuSE.
I took imapd.conf and cyrus.conf and changed the paths to f
On Thu, 12 Jan 2006, Cap wrote:
One more thing about this...
Is it possible to configure cyrus to contact SASL in a non
standard way, let's say through a domain socket specified
by an explicit path?
sasl_saslauthd_path
See $cyrus-sasl/doc/options.html
This works great so far, althoug
On Thu, 12 Jan 2006, Cap wrote:
One more thing about this...
Is it possible to configure cyrus to contact SASL in a non
standard way, let's say through a domain socket specified
by an explicit path?
sasl_saslauthd_path
See $cyrus-sasl/doc/options.html
This works great so far, although
One more thing about this...
> >>> Is it possible to configure cyrus to contact SASL in a non
> >>> standard way, let's say through a domain socket specified
> by an explicit path?
> sasl_saslauthd_path
> See $cyrus-sasl/doc/options.html
This works great so far, although I do need two differe
On Tue, 10 Jan 2006, Cap wrote:
Hi again,
Is it possible to configure cyrus to contact SASL in a non
standard way, let's say through a domain socket specified by
an
explicit path?
--- Igor Brezac <[EMAIL PROTECTED]> wrote:
Yes (I assume you are trying to connect to saslauthd?)
Yes th
Hi again,
> > Is it possible to configure cyrus to contact SASL in a non
> > standard way, let's say through a domain socket specified by
> an
> > explicit path?
--- Igor Brezac <[EMAIL PROTECTED]> wrote:
> Yes (I assume you are trying to connect to saslauthd?)
Yes that's what I'm trying. I wa
On Mon, 9 Jan 2006, Cap wrote:
Hi!
I'm using SASL with postfix to authenticate users for smtp. I
also would like to use SASL with Cyrus to authenticate imap
users against LDAP, but in this case SASL needs a _different_
condfiguration.
Is it possible to configure cyrus to contact SASL in a non
Hi!
I'm using SASL with postfix to authenticate users for smtp. I
also would like to use SASL with Cyrus to authenticate imap
users against LDAP, but in this case SASL needs a _different_
condfiguration.
Is it possible to configure cyrus to contact SASL in a non
standard way, let's say through a
Hi!
Jesus Ruiz schrieb am 16.08.2005 23:42:
Hi, i have been trying to install the cyrus-imapd to authenticate
through sasl and i need sasl read it data from a ldap server. I'm
running redhat AS 4
#authentication ldap
sasl_pwcheck_method: saslauthd
Why don't you use ldapdb here
sasl_pwcheck_m
Hi, i have been trying to install the cyrus-imapd to authenticate
through sasl and i need sasl read it data from a ldap server. I'm
running redhat AS 4
I manage to make work the sasl-2.1.21 with openldap-2.2.27
I compiled the sasl with this options:
./configure --prefix=/usr \
--with-plugind
Wow, I feel stupid now. That looks like it was it.
Thanks.
ldap_filer: [EMAIL PROTECTED]
Check your spelling.
This does not work, however, but if I have a uid attribute set in
ldap in the form of: [EMAIL PROTECTED], authentication works.
Is it possible to use the mail attribute to authenticate,
On Tue, 3 May 2005, AJ wrote:
Trying to set up both saslauthd and cyrus-imapd for virtual domain support.
I would like to authenticate against the LDAP mail attribute, so I use this
in saslauthd.conf:
ldap_filer: [EMAIL PROTECTED]
Check your spelling.
This does not work, however, but if I have a
Trying to set up both saslauthd and cyrus-imapd for virtual domain support.
I would like to authenticate against the LDAP mail attribute, so I use
this in saslauthd.conf:
ldap_filer: [EMAIL PROTECTED]
This does not work, however, but if I have a uid attribute set in ldap
in the form of: [EMAIL
Julian W H Osborne wrote:
Thanks Andy,
In making various changes since the first post I had changed it to yes.
Changed it back with the other changes and it all works :-)
Julian
What you changed to yes to got it working? I'm having the same problem, %r
in
sasl_sql_statement doesnt got substitut
Just a quick thanks you to Andy, Igor and Ondrey, for the help. Have it
working now.
Thanks Guys.
Julian
Julian W H Osborne wrote:
Dear All,
I'm having some problems getting Cyrus imap to work correctly with sasl
and ldap. Using the testsaslauthd command all is okay, username and domain
is passe
Thanks Andy,
In making various changes since the first post I had changed it to yes.
Changed it back with the other changes and it all works :-)
Julian
Andy Fiddaman wrote:
Have you got:
virtdomains: userid
in the imapd.conf ?
On Wed, 16 Mar 2005, Julian W H Osborne wrote:
; OndÅej SurÃ
OndÅej Surà wrote:
On Tue, 2005-03-15 at 16:56 +, Julian W H Osborne wrote:
Dear All,
I'm having some problems getting Cyrus imap to work correctly with sasl
and ldap. Using the testsaslauthd command all is okay, username and domain
is passed through. However, when using the imap or pop clie
OndÅej Surà wrote:
On Tue, 2005-03-15 at 16:56 +, Julian W H Osborne wrote:
Dear All,
I'm having some problems getting Cyrus imap to work correctly with sasl
and ldap. Using the testsaslauthd command all is okay, username and domain
is passed through. However, when using the imap or pop clie
On Tue, 2005-03-15 at 16:56 +, Julian W H Osborne wrote:
> Dear All,
>
> I'm having some problems getting Cyrus imap to work correctly with sasl
> and ldap. Using the testsaslauthd command all is okay, username and domain
> is passed through. However, when using the imap or pop client only
Igor Brezac wrote:
On Tue, 15 Mar 2005, Julian W H Osborne wrote:
Dear All,
I'm having some problems getting Cyrus imap to work correctly with
sasl and ldap. Using the testsaslauthd command all is okay, username
and domain
is passed through. However, when using the imap or pop client only
the
On Tue, 15 Mar 2005, Julian W H Osborne wrote:
Dear All,
I'm having some problems getting Cyrus imap to work correctly with sasl and
ldap. Using the testsaslauthd command all is okay, username and domain
is passed through. However, when using the imap or pop client only the user
part of the log
Dear All,
I'm having some problems getting Cyrus imap to work correctly with sasl
and ldap. Using the testsaslauthd command all is okay, username and domain
is passed through. However, when using the imap or pop client only the
user part of the login name is passed through, e.g. if username is
On Tue, 25 May 2004, Kent L. Nasveschuk wrote:
> I am trying to compile Cyrus-SASL with LDAP support and OpenLDAP with
> Cyrus-SASL support. I want to use saslauthd for IMAP users to
> authenticate to our OpenLDAP directory. The problem is that each seems
> to be dependent on the other.
>
>
>
>
I am trying to compile Cyrus-SASL with LDAP support and OpenLDAP with
Cyrus-SASL support. I want to use saslauthd for IMAP users to
authenticate to our OpenLDAP directory. The problem is that each seems
to be dependent on the other.
Anyone have some ideas on this? I'm doing this on a Slackware 9
On Fri, 21 May 2004, Andrew B. Panphiloff wrote:
> I have strange behaviour of cyrus-imapd and cyrus-sasl.
>
> imapd config :
>
> --
> tls_ca_file: /etc/ssl/cyrus.pem
> tls_cert_file: /etc/ssl/cyrus.pem
> tls_key_file: /etc/
On Fri, 21 May 2004, Andrew B. Panphiloff wrote:
why in first case saslauthd get "[EMAIL PROTECTED]" and "realm="
but in second case it get "user=jeka" and "realm=8ka.mipt.ru" ?
How fix this behaviour ?
Because SASL treats everything after the @ sign as a 'realm'.
You'll need to fix your filter acc
I have strange behaviour of cyrus-imapd and cyrus-sasl.
imapd config :
--
tls_ca_file: /etc/ssl/cyrus.pem
tls_cert_file: /etc/ssl/cyrus.pem
tls_key_file: /etc/ssl/cyrus.pem
virtdomains: yes
defaultdomain: localhost
configdir
On Wed, 24 Mar 2004, zorg wrote:
> hi,
> here is my problem,
> I want cyrus to use the login and password from my ldap server
>
> I manage to make it work using
> saslauthd +pam +ldap
> or
> saslauthd + ldap
>
> in both case I can only use the plaintext authentification
>
> it seem normal for the
hi,
here is my problem,
I want cyrus to use the login and password from my ldap server
I manage to make it work using
saslauthd +pam +ldap
or
saslauthd + ldap
in both case I can only use the plaintext authentification
it seem normal for the pam solution
but maybe there is more to do to make it wo
On Tue, 29 Oct 2002, Gregory Chagnon wrote:
> Thanks Igor, that helped a little...now it looks like it's being
> authenticated against the LDAP database and getting granted access.
> However, when I run imtest -m login -a cliff.clavin localhost, I get this:
>
> [root@Lunar]:/usr/src/cyrus-sasl-2.
29 15:04:10 Lunar slapd[11016]: => id2entry_r( 26 )
Oct 29 15:04:10 Lunar slapd[11016]: > cache_find_entry_id( 26 )
"uid=cliff.clavin,ou=Users,dc=gregbox,dc=com" (found) (1 tries)
Oct 29 15:04:10 Lunar slapd[11016]: <= id2entry_r( 26 ) 0x8189108 (cache)
Oct 29 15:04:10 Lunar s
<[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: Gregory Chagnon <[EMAIL PROTECTED]>
> >CC: [EMAIL PROTECTED]
> >Subject: Re: cyrus-sasl / ldap problem
> >Date: Tue, 29 Oct 2002 10:52:59 -0500 (EST)
> >
> >
> >It looks like saslauthd
ROTECTED]
> >To: Gregory Chagnon <[EMAIL PROTECTED]>
> >CC: [EMAIL PROTECTED]
> >Subject: Re: cyrus-sasl / ldap problem
> >Date: Tue, 29 Oct 2002 10:52:59 -0500 (EST)
> >
> >
> >It looks like saslauthd is not running or testsaslauthd is pointing to a
Where is that set?
-Greg
From: Igor Brezac <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: Gregory Chagnon <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: cyrus-sasl / ldap problem
Date: Tue, 29 Oct 2002 10:52:59 -0500 (EST)
It looks like saslauthd is not running or testsa
cket
as well?
-Greg
From: Igor Brezac <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: Gregory Chagnon <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: cyrus-sasl / ldap problem
Date: Tue, 29 Oct 2002 10:52:59 -0500 (EST)
It looks like saslauthd is not running or tests
.
-Greg
From: Igor Brezac <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: Gregory Chagnon <[EMAIL PROTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: cyrus-sasl / ldap problem
Date: Tue, 29 Oct 2002 10:52:59 -0500 (EST)
It looks like saslauthd is not running or testsaslauthd is poi
file or directory
>
>
>
>
>
>
>
> >From: Igor Brezac <[EMAIL PROTECTED]>
> >Reply-To: [EMAIL PROTECTED]
> >To: Gregory Chagnon <[EMAIL PROTECTED]>
> >CC: [EMAIL PROTECTED]
> >Subject: Re: cyrus-sasl / ldap problem
> >Date: Tue, 29 Oct 2002 09
egory Chagnon"
<[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: cyrus-sasl / ldap problem
Date: Tue, 29 Oct 2002 08:52:40 -0500
Hi:I'm having a problem getting Cyrus IMAP to work with OpenLDAP.
User cliff.clavin is under ou=Users,dc=gregbox,dc=com. When I run
imtest, here is the
OTECTED]>
CC: [EMAIL PROTECTED]
Subject: Re: cyrus-sasl / ldap problem
Date: Tue, 29 Oct 2002 09:22:22 -0500 (EST)
Test saslauthd first. cd $cyrus-sasl-src/saslauthd; make testsaslauthd
./testsaslauthd -u username -p password
If you do not get OK, check syslog for saslauthd errors.
-Igor
On T
One thing I left out, here is an entry from /var/log/auth.log which is
entered everytime I try imtest:
Oct 29 09:31:37 Lunar imapd[5495]: cannot connect to saslauthd server: No
such file or directory
From: "Gregory Chagnon" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Sub
Test saslauthd first. cd $cyrus-sasl-src/saslauthd; make testsaslauthd
./testsaslauthd -u username -p password
If you do not get OK, check syslog for saslauthd errors.
-Igor
On Tue, 29 Oct 2002, Gregory Chagnon wrote:
> Hi:I'm having a problem getting Cyrus IMAP to work with OpenLDAP. User
>
Hi:I'm having a problem getting Cyrus IMAP to work with OpenLDAP. User
cliff.clavin is under ou=Users,dc=gregbox,dc=com. When I run imtest, here
is the error I get...thanks everyone so much in advance:
[root@Lunar]:/home/gchagnon> imtest -m login -a cliff.clavin localhost
S: * OK Lunar Cyrus I
Rob Siemborski wrote:
>
> On Tue, 15 Oct 2002, Gardiner Leverett wrote:
>
> > Great! I'll go try that first. Is there any documentation for the saslauth
> > db file? According to the web docs included with the source, it says to
> > check the man page for saslauthdb, but when I do, I get an in
On Tue, 15 Oct 2002, Gardiner Leverett wrote:
> Great! I'll go try that first. Is there any documentation for the saslauth
> db file? According to the web docs included with the source, it says to
> check the man page for saslauthdb, but when I do, I get an incomplete
> page without the necessa
Rob Siemborski wrote:
>
> On Tue, 15 Oct 2002, Gardiner Leverett wrote:
>
> > After fussing around with the make files so that cyrus-sasl would
> > actually include the pam library, cyrus still doesn't have the library
> > on compile, and trying to test the server produces no result.
>
> I'm
On Tue, 15 Oct 2002, Gardiner Leverett wrote:
> After fussing around with the make files so that cyrus-sasl would
> actually include the pam library, cyrus still doesn't have the library
> on compile, and trying to test the server produces no result.
I'm not sure why you have to use PAM. Saslau
I know it seems like a lot, but here's the task I'm working with:
We have a FreeBSD 4.7 machine and we're trying to use
OpenLDAP 2.0.25, cyrus-sasl-2.1.7, and cyrus-imap.2.1.9. To get
Cyrus to use LDAP for authentication, we need a pam module,
and we're using pam_ldap-1.5.2. (All of this using
Many, many thanks for this one :)
I downloaded and applied it to my system and it worked without any hassle. Very
nice :)
Simon Loader wrote:
> Can I get the users password to be able to bind with ? or
> should I just do anonymous ?
You mean so you can use ldap acls on the bind operation?
Tarj
>
> We use SASL1->LDAP in a clusterd HA environment with the LDAP patch supplied by
> http://www.surf.org.uk/src/cyrussasl.html which AFAIK does not support multiple
> LDAP servers. We are at the moment suggensting a switch to SASL1->PAM->LDAP,
> which is not as fast, but will support multiple
> What do you mean, using multiple A records in round-robin? I think
> that's required, or at least, recommended behaviour. I don't know
> exactly how much benefit there is to being able to list multiple
> servers in a configuration file over being able to list multiple
> servers in DNS. Perhap
Also Sprach Birger Toedtmann:
> Why that? SASL awaits its OK from PAM - which LDAP server PAM itself
> connected to is not SASLs business. (to avoid misunderstanding:
> we won't mix both methods, no).
Okay, I didn't look closely at the FAQ that explained why that was
happening, I just avoided
Wil Cooley schrieb am Sun, Nov 25, 2001 at 12:36:33AM -0800:
* Also Sprach Birger Toedtmann:
^^^- whooa I'm not Nietzsche. Far from it. ;-)
*
* > We use SASL1->LDAP in a clusterd HA environment with the LDAP patch
* > supplied by http://www.surf.org.uk/src/cyrussasl.html which AF
Also Sprach Birger Toedtmann:
> We use SASL1->LDAP in a clusterd HA environment with the LDAP patch
> supplied by http://www.surf.org.uk/src/cyrussasl.html which AFAIK does
> not support multiple LDAP servers. We are at the moment suggensting
> a switch to SASL1->PAM->LDAP, which is not as fast,
Kevin J. Menard, Jr. schrieb am Sat, Nov 24, 2001 at 11:30:36AM -0500:
[...]
* JW> Most of the LDAP libraries (for sure OpenLDAP which is what we are using) allow
* JW> you to specify multiple redundant LDAP servers in the list separated by spaces.
*
* If there's enough requests for it, I'll t
Hi Kevin,
Most of the LDAP libraries (for sure OpenLDAP which is what we are using) allow
you to specify multiple redundant LDAP servers in the list separated by spaces.
This works in a failover configuration. If a query to the first times out, it
goes to the second, then the third, etc. W
At 13:29 24/10/01 -0400, Kevin M. Myer wrote:
>Short of that, what are folks doing in terms of
>high-availiblity/redundancy for
>LDAP? I've thought through scenarios of using heartbeat to determine which
>machines are up and updating DNS accordingly. I also suppose you could do
>something with
There's dns capability to combine roundrobin querys with a "servicename" I
think. Thus you can point to "ldapserver" and the dns will send your query to
the server that's up and running. I never tried it myself, but you'll find it at
www.bayour.com in the ldap-kerberos howto :=)
Tarjei
"Kevin M.
Title: SASL-LDAP Patch = Ahhh!
Hey All,
So Im trying to compile Cyrus-sasl with the SASL-Auth-LDAP patch (http://sourceforge.net/projects/cyrus-utils/) and cyrus-sasl 1.5.24.
I untar everything and run:
patch -p1 < sasl-ldap+mysql.patch
autoheader
autoconf
automake -i
export CPPFL
Hello,
I'm using the patch that allows LDAP authentication with the SASL libraries. Is
there a way to specify multiple servers to bind to so that in the event that a
directory server becomes unavailable, a backup could be used?
Short of that, what are folks doing in terms of high-availiblity/re
Hey Norbert,
Thursday, July 19, 2001, 8:41:58 AM, you wrote:
NK> Hi,
>> Well, as stated earlier, here's my patch. It is based on Simon
>> Loader's code. I did nothing new to the MySQL code. There are
>> several changes to his LDAP code, but really, I just added search
>> cap
Hey guys,
Well, as stated earlier, here's my patch. It is based on Simon
Loader's code. I did nothing new to the MySQL code. There are
several changes to his LDAP code, but really, I just added search
capability to it.
I've also added three new directives. ldap_filter wil
73 matches
Mail list logo
