Re: NTFS Permissions
From: Brian Boynton (bboynton3@hotmail.com)
Date: 05/30/02
- Next message: Nick Wilson: "Authentication within Authentication in .NET"
- Previous message: John: "Re: deleting "tagged" files"
- Next in thread: IT Community: "Re: NTFS Permissions"
- Reply: IT Community: "Re: NTFS Permissions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Brian Boynton" <bboynton3@hotmail.com> Date: Thu, 30 May 2002 13:02:20 -0400
Hello,
I have a basic question about permissions for an Intranet page I'm setting
up.
The intranet page we're setting up will have links to various department
pages. For the sake of an example, let's say I want to restrict access to
the EXEC page to the EXEC group. The easiest way to go about this would be
to use the NTFS Security Tab on the Folder itself. The EXEC group now has
Read/Write permissions to that folder within Inetpub
(c:\inetpub\intranet_site\Exec).
All of this time I've enabled the anonymous user login usage for the
Intranet Virtual Directory. However, if I use Windows Integrated
Authentication, I get a three-line login prompt, when trying to gain
access,
which no EXECUTIVE, after using their login, password, and domain
specification as instructed, can get past. (the dialog prompt just repeats
three times and I get the unauthorized page message)
If I apply DOMAIN USERS to the NTFS permissions for the EXEC folder, THEN
EVERYONE can get in. So at least I can get access to the page, but now
EVERYONE has access.
If I go back to the Virtual Directory Security and use Basic Authentication
(specifying the domain after typing EDIT) instead of Windows Integrated
Authentication, then I only get a two line prompt, logically, and the
EXECUTIVE can log in with just their username and password.
What the hell is going in with this Windows Integrated authentication?
Other things I've noticed with Windows Integrated authentication...is if
You're logged into the domain ALREADY, and a 3-line dialog box pops up, it
never works. But if you're logged into a workstation machine as a LOCAL
USER, and the 3-line security login-pops up...you can log in.
I experimented with the Anonymous User I'm using (which is a domain
Anonymous user), making it a member of the EXEC group, etc. That doesn't
work.
Any feedback would be greatly appreciated.
At this point I'm happy with the Basic Authentication, but I'd prefer a
functioning transparent login for users. (plus something that's a little
more secure, even though this is an intranet page)
Thanks,
Brian
- Next message: Nick Wilson: "Authentication within Authentication in .NET"
- Previous message: John: "Re: deleting "tagged" files"
- Next in thread: IT Community: "Re: NTFS Permissions"
- Reply: IT Community: "Re: NTFS Permissions"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|