Hi all,
we have a problem with the HTTP Proxy using usery from Active Directory/NT Domain Membership.
Mainly the httpProxy works fine, but before last week we had only 1 User with a name like "???.?ü???" created in NT as "???.?ue???". This user had all the times problems to login into the proxy. It never works. So we have creaded a special users account for him, to acccess the proxy.
Now since last week we got an other problem ;-) We got a new employee with a similar name like the user above. The username is again like "???.?ü???" and the NT-Account is "???.?ue???". And again, this user doesn't work.
So now we have 2 useres doesn't work?!?!?
Does somebody similar problems?
This is our configuration ASL 5.100:
1.System >> User Authentication:
Active Directory/NT Domain Membership:
Status == enabled
Domain member status == Joined domain xyz.
Domain == xyz
Firewall NetBIOS hostname == ASL5
LDAP Server Settings:
Status == enabled
LDAP Type == Active D
Unique User Attribute == sAMAccountName
IP Address == 192.168.0.1
TCP Port == 389
Bind DN == user@xyz.de
Base DN == DC=xyz,DC=de
Password == ****
LDAP Authentication by Attribute == enabled
Service Attribute Name Attribute Value
http memberof CN=HTTP_User,CN=Builtin,DC=xyz,DC=de
2.Proxies >> HTTP
Global Settings:
Status == enabled
Operation Mode == User Auth
Log Level == Full
Anonymity == none
Allowed Networks == our_LAN
User Authentication:
Authentication Methods == 1 LDAP Directory
Content Filter (Surf Protection):
Whitelist domains == ebay.de
Profiles:
Profile Assignment via == LDAP Directory Local Users
HTTP_Admin == CN=HTTP_Admin,CN=Builtin,DC=xyz,DC=de
HTTP_NoWebmail == CN=HTTP_NoWebmail,CN=Builtin,DC=xyz,DC=de
This configuration works for all our Users, apart from this both above
Any Ideas??? Do we have a configuration problem?
TIA
Marc
This thread was automatically locked due to age.
