|
 |
asp_web_howto thread: how to give / deny access to certain parts an intranet ?
Message #1 by "Sander van der Kooij" <svdkooij@c...> on Wed, 24 Apr 2002 19:24:24
|
|
Hi all.
How can asp-script help me to block out certain pages from our intranet.
Lets say 'domain users' my not access pages that contain information used
by 'accountant' from the financial department.
Those groups exists in our domain. I know I can turn on NT authentication
only and apply the proper NTFS rights but a nasty access denied error
will occur. How can I, based on the group-membership, hide links or make
them visible.. We don't want to use and 3rd party components..
Is there a document available about this. I assume i'm not the only one
with this question..
Regards
Sander
Message #2 by Jack_Speranza <jsperanza@g...> on Wed, 24 Apr 2002 14:23:03 -0400
|
|
If your only concern lies with the standard error page that's returned when
access is denied, why not just create your own custom error page and stick
with NT security (the best solution, IMHO). If you're primarily concerned
with actually hiding links, not sure there's an easy way to manage this
outside of coding a security scheme into your application (you could still
rely on NT security to some degree, but I don't think ASP lets you access
role information, etc., unless you custom build something to access an
Active Directory or do something along those lines... but I could be wrong,
here).
Hope this helps.
Jack
-----Original Message-----
From: Sander van der Kooij [mailto:svdkooij@c...]
Sent: Wednesday, April 24, 2002 3:24 PM
To: ASP Web HowTo
Subject: [asp_web_howto] how to give / deny access to certain parts an
intranet ?
Hi all.
How can asp-script help me to block out certain pages from our intranet.
Lets say 'domain users' my not access pages that contain information used
by 'accountant' from the financial department.
Those groups exists in our domain. I know I can turn on NT authentication
only and apply the proper NTFS rights but a nasty access denied error
will occur. How can I, based on the group-membership, hide links or make
them visible.. We don't want to use and 3rd party components..
Is there a document available about this. I assume i'm not the only one
with this question..
Regards
Sander
---
Improve your web design skills with these new books from Glasshaus.
Usable Web Menus
http://www.amazon.com/exec/obidos/ASIN/1904151027/ref=nosim/theprogramme
r-20
Constructing Accessible Web Sites
http://www.amazon.com/exec/obidos/ASIN/1904151000/ref=nosim/theprogramme
r-20
Practical JavaScript for the Usable Web
http://www.amazon.com/exec/obidos/ASIN/1904151051/ref=nosim/theprogramme
r-20
Message #3 by "Sander van der Kooij" <svdkooij@c...> on Wed, 24 Apr 2002 20:39:51
|
|
So I would enable NTCR...
Changing the error pages isn't that hard.. but is would be more friendly
if the link is not visible at all for those who do not need to be there...
Regards
Sander
> If your only concern lies with the standard error page that's returned
when
access is denied, why not just create your own custom error page and stick
with NT security (the best solution, IMHO). If you're primarily concerned
with actually hiding links, not sure there's an easy way to manage this
outside of coding a security scheme into your application (you could still
rely on NT security to some degree, but I don't think ASP lets you access
role information, etc., unless you custom build something to access an
Active Directory or do something along those lines... but I could be
wrong,
here).
Hope this helps.
Jack
Message #4 by Jack_Speranza <jsperanza@g...> on Wed, 24 Apr 2002 16:59:19 -0400
|
|
I agree, however, unless you devise another scheme with which to integrate
your NT security into your ASP application, this means you will have to
administer two separate security paradigms (one for your app, and the
existing NT scheme). Central administration generally makes for a better
application, and this is why I believed sticking with an NT security
solution was best.
-----Original Message-----
From: Sander van der Kooij [mailto:svdkooij@c...]
Sent: Wednesday, April 24, 2002 4:40 PM
To: ASP Web HowTo
Subject: [asp_web_howto] RE: how to give / deny access to certain parts
an intranet ?
So I would enable NTCR...
Changing the error pages isn't that hard.. but is would be more friendly
if the link is not visible at all for those who do not need to be there...
Regards
Sander
> If your only concern lies with the standard error page that's returned
when
access is denied, why not just create your own custom error page and stick
with NT security (the best solution, IMHO). If you're primarily concerned
with actually hiding links, not sure there's an easy way to manage this
outside of coding a security scheme into your application (you could still
rely on NT security to some degree, but I don't think ASP lets you access
role information, etc., unless you custom build something to access an
Active Directory or do something along those lines... but I could be
wrong,
here).
Hope this helps.
Jack
---
Improve your web design skills with these new books from Glasshaus.
Usable Web Menus
http://www.amazon.com/exec/obidos/ASIN/1904151027/ref=nosim/theprogramme
r-20
Constructing Accessible Web Sites
http://www.amazon.com/exec/obidos/ASIN/1904151000/ref=nosim/theprogramme
r-20
Practical JavaScript for the Usable Web
http://www.amazon.com/exec/obidos/ASIN/1904151051/ref=nosim/theprogramme
r-20
|
|
 |