|
Home > Archive > Squid > April 2004 > [squid-users] Problem with squid_ldap_auth
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[squid-users] Problem with squid_ldap_auth
|
|
| ashish.uchil@tcs.com 2004-04-30, 5:36 am |
|
This is a multi-part message in MIME format.
------=_NextPartTM-000-f06f91ef-b77e-45a5-93b3-f1167c19a04d
Content-type: text/plain; charset=US-ASCII
Hi all
I am using squid_ldap_auth to authenticate users in a Win 2k Domain .
I can authenticate users which have authority to log on to all workstations
..
If an user which has authority to log on to only selected workstation fails
authentication with the squid_ldap_auth.
I have tried including squid servers hostname and IP address in the list of
workstations the user can log on to,but no luck.
Could anyone please help me with how i can authenticate such users as all
my windows users are authorized to authenticate only to their desktop.
Would be grateful if anyone can suggest a resolution.
Thanks in advance.
With Warm Regards
Ashish Uchil
Tata Consultancy Services
C - 56, Phase 2
Noida,Uttar Pradesh
India
Phone :: +91-120-2461932
Mailto: ashish.uchil@tcs.com
Website: http://www.tcs.com
------=_NextPartTM-000-f06f91ef-b77e-45a5-93b3-f1167c19a04d
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
name="InterScan_Disclaimer.txt"
Content-Disposition: attachment;
filename="InterScan_Disclaimer.txt"
DISCLAIMER: The information contained in this message is intended only and solely for the addressed individual or entity indicated in this message and for the exclusive use of the said addressed individual or entity indicated in this message (or responsib
le for delivery
of the message to such person) and may contain legally privileged and confidential information belonging to Tata Consultancy Services. It must not be printed, read, copied, disclosed, forwarded, distributed or used (in whatsoever manner) by any person oth
er than the
addressee. Unauthorized use, disclosure or copying is strictly prohibited and may constitute unlawful act and can possibly attract legal action, civil and/or criminal. The contents of this message need not necessarily reflect or endorse the views of Tata
Consultancy Services
on any subject matter. Any action taken or omitted to be taken based on this message is entirely at your risk and neither the originator of this message nor Tata Consultancy Services takes any responsibility or liability towards the same. Opinions, conclu
sions and any other
information contained in this message that do not relate to the official business of Tata Consultancy Services shall be understood as neither given nor endorsed by Tata Consultancy Services or any affiliate of Tata Consultancy Services. If you have receiv
ed this message in error,
you should destroy this message and may please notify the sender by e-mail. Thank you.
------=_NextPartTM-000-f06f91ef-b77e-45a5-93b3-f1167c19a04d--
| |
| Henrik Nordstrom 2004-04-30, 5:36 am |
| On Fri, 30 Apr 2004 ashish.uchil@tcs.com wrote:
> If an user which has authority to log on to only selected workstation fails
> authentication with the squid_ldap_auth.
This is correct, and how Windows policies works..
> I have tried including squid servers hostname and IP address in the list of
> workstations the user can log on to,but no luck.
Unfortunately I do not know enough of Windows policies to tell how to add
access to non-member stations.. Should be the same method as adding access
to log in from a Windows 9x station I think as these are also "random
stations not member of the domain".
Another option if no solution to this is found is to authenticate via
Samba winbind. When this method is used the Squid server becomes a full
member of the domain, just like any other server or station. This should
make it easier to add login rights to Squid. See the Squid FAQ on how to
configure Squid to use winbind.
Regards
Henrik
|
|
|
|
|