Hi, really, it works ! I am apologize, not buggy soft, but buggy configuration ! Now right configuration is ... Delegated start: PROXY_SERVER# delegated -P389 SERVER=ldap FSV=sslway ADMIN=root Command to test it: TEST_SERVER# ldapsearch -h PROXY_SERVER -b dc=gov@LDAPS_SERVER:636 cn=test* Thanks a lot, support more&more better than M$ ... :} Cheers, Jarek -----Original Message----- From: feedback@delegate.org [mailto:feedback@delegate.org] Sent: Friday, March 30, 2001 9:49 AM To: feedback@delegate.org Cc: pfecabdyi-rcwevegyz7tr.ml@ml.delegate.org Subject: Re: [DeleGate-En] Delegated and LDAPS Hi, |I tried it, but again it doesn solve it :( | |Delegated start: |# delegated -P389 SERVER=ldaps FSV=sslway ADMIN=root PERMIT="*:*:*" "SERVER=ldaps" means that the client-side protocol is "ldaps", but it is not so in your case. You should specify SERVER="ldap". see <URL:/delegate/Manual.htm#SERVER> for more details. |03/30 08:50:53.96 [6922] 3+0: E-P: No permission: lnxtest.anect.com:3449 => |ldap://makrela.anect.cz:636 I hope this problem will be fixed with SERVER=ldap |4. Thanks a lot for yuor answer and great software (maybe with a |little bugs:)) It can be called a bug in the meaning that, when it is used as a "LDAPS" server for LDAPS client, it rejects LDAPS accesses to be permitted, given with SERVER=ldaps FCL=sslway, and without REMITTABLE="+,ldap" Cheers, Yutaka -- Yutaka Sato <ysato@delegate.org> http://www.delegate.org/~ysato/ @ @ Computer Science Division, Electrotechnical Laboratory ( - ) 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan _< >_