Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 1 reply
  • Subscribers 2 subscribers
  • Views 518 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ASL V5.0 LDAP Authentication for HTTP Proxy

JCB
LDAP Authentication for HTTP Proxy and SMTP does not seem to work in V5.0

Here are the entries from the aua log when I try to authenticate onto the HTTP Proxy:
2004:04:10-08:40:24 (none) aua[14849]: no such facility: http
2004:04:10-08:40:24 (none) aua[14849]: U:jcbiosa F:http R[:D]ENY

SMTP Authentication does not work either and I get a relay not permitted in the SMTP log.

Furthermore, my LDAP server does not receive any transaction - it was working in V4.0


This thread was automatically locked due to age.
Parents
  • 0
    I upgraded to 5.001 yesterday and I can see now LDAP transactions coming from ASL in my LDAP Server logs.
    Unfortunately if I use an unknown user, at the 2nd login attempt ASL goes back to mumm and authorizes the access.

    This affects HTTP Proxy, Socks and SMTP authentication. 

    Again everything was working fine in ASL4 - very disapointing.. User authentication is such a basic feature.
Reply
  • 0
    I upgraded to 5.001 yesterday and I can see now LDAP transactions coming from ASL in my LDAP Server logs.
    Unfortunately if I use an unknown user, at the 2nd login attempt ASL goes back to mumm and authorizes the access.

    This affects HTTP Proxy, Socks and SMTP authentication. 

    Again everything was working fine in ASL4 - very disapointing.. User authentication is such a basic feature.
Children
No Data