List Info

Thread: kolab with ldaps (port 636) ?




kolab with ldaps (port 636) ?
country flaguser name
India
2007-03-13 00:28:00
Dear list,

Can Kolab use port 636 (ldaps) with TLS enabled ? 
OR    ldap (port 389) with TLS enabled ?

I have tried to configure Kaddress book to talk with port
636 but it is
not working
while it has no problem to work with port 389.

thanks

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Re: kolab with ldaps (port 636) ?
country flaguser name
Germany
2007-03-13 01:56:50
JOYDEEP <j.bakshiunlimitedmail.org> writes:

> Dear list,
>
> Can Kolab use port 636 (ldaps) with TLS enabled ? 
> OR    ldap (port 389) with TLS enabled ?

it should by default listen on both ports:

root# grep openldap_url /kolab/etc/rc.conf
openldap_url="ldap:// ldaps://"

And netstat shows the open port:

netstat -lnp | grep 636
tcp        0      0 0.0.0.0:636             0.0.0.0            
  LISTEN      22102/slapd       

So your probably configured something in your client in an
incorrect
way.

Cheers,

Gunnar
-- 
____ http://www.pardus.de
_________________ http://gunnarwrobel.de _

    >> Mail at ease - Rent a kolab groupware server at
prdus <<

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Re: kolab with ldaps (port 636) ?
country flaguser name
India
2007-03-13 02:43:05
Gunnar Wrobel wrote:
> JOYDEEP <j.bakshiunlimitedmail.org>
writes:
>
>   
>> Dear list,
>>
>> Can Kolab use port 636 (ldaps) with TLS enabled ? 
>> OR    ldap (port 389) with TLS enabled ?
>>     
>
> it should by default listen on both ports:
>
> root# grep openldap_url /kolab/etc/rc.conf
> openldap_url="ldap:// ldaps://"
>
> And netstat shows the open port:
>
> netstat -lnp | grep 636
> tcp        0      0 0.0.0.0:636             0.0.0.0            
  LISTEN      22102/slapd       
>
> So your probably configured something in your client in
an incorrect
> way.
>
> Cheers,
>   
Thanks, I also have port 636 open here. but can I use kolab
to listen
636 ?  more over kaddressbook is not working with 636 but
with 389.

> Gunnar
>   

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Re: kolab with ldaps (port 636) ?
country flaguser name
Germany
2007-03-13 03:10:53
JOYDEEP <j.bakshiunlimitedmail.org> writes:

>> And netstat shows the open port:
>>
>> netstat -lnp | grep 636
>> tcp        0      0 0.0.0.0:636            
0.0.0.0
              LISTEN      22102/slapd       
>>
> Thanks, I also have port 636 open here. but can I use
kolab to listen
> 636 ?  

If you have port 636 open and it is listed in the netstat
output, then
Kolab is indeed listening on that port. Nothing additional
is required.

>> So your probably configured something in your
client in an incorrect
>> way.
>>
> more over kaddressbook is not working with 636 but with
389.

As I mentioned this is probably a configuration problem with
your
client. Try checking with another client first. Use luma
for
example. You can also go into debugging mode with you LDAP
server and
check what happens on the server side (see
http://wiki.kolab.org/index.php/Kolab2_Serve
r_Troubleshooting_-_LDAP).

Cheers,

Gunnar

-- 
____ http://www.pardus.de
_________________ http://gunnarwrobel.de _

    >> Mail at ease - Rent a kolab groupware server at
prdus <<

prdus Kolab work is funded in part by KDAB and the
Kolab Konsortium

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

Re: kolab with ldaps (port 636) ?
country flaguser name
Germany
2007-03-22 10:16:48
On Tuesday 13 March 2007 08:43, JOYDEEP wrote:
> but can I use kolab to listen 636 ?  

Sure Kolab Clients should support this.

> more over kaddressbook is not working with 636 but with
389. 

Try the "Improved LDAP resource".
It might be interesting to investigate if the simple search
interface can also 
do TLS/SSL.

Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free
Software Company)
Germany Coordinator: fsfeurope.org. Coordinator:
www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB
18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr.
Jan-Oliver Wagner

_______________________________________________
Kolab-users mailing list
Kolab-userskolab.org
https:
//kolab.org/mailman/listinfo/kolab-users

[1-5]

about | contact  Other archives ( Real Estate discussion Medical topics )