HighTechTalks DotNet Forums  

How to bypass Forms Authentication on selected pages programmatica

Dotnet Security microsoft.public.dotnet.security


Discuss How to bypass Forms Authentication on selected pages programmatica in the Dotnet Security forum.



Reply
 
Thread Tools Search this Thread Display Modes
  #1  
Old   
ajmehra
 
Posts: n/a

Default How to bypass Forms Authentication on selected pages programmatica - 02-13-2007 , 01:52 PM






Hi

I am trying to bypass Forms Authentication on certain pages
programmatically. Any thoughts will be appreciated.

Thanks,
AJ

Reply With Quote
  #2  
Old   
Joe Kaplan
 
Posts: n/a

Default Re: How to bypass Forms Authentication on selected pages programmatica - 02-13-2007 , 01:57 PM






Use the HttpContext.SkipAuthorization property to turn authorization on or
off programmatically on a page by page basis. You probably want to put this
code in global.asax or an IHttpModule.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote

Quote:
Hi

I am trying to bypass Forms Authentication on certain pages
programmatically. Any thoughts will be appreciated.

Thanks,
AJ



Reply With Quote
  #3  
Old   
ajmehra
 
Posts: n/a

Default Re: How to bypass Forms Authentication on selected pages programma - 02-13-2007 , 02:31 PM



Thanks Joe.

Do you have an example of this property being used in Global.asax? I am not
sure about how to check to see if -- this is the right page to be left out
for authentication.

Should I use a QueryString for this check?


Thanks again
AJ

"Joe Kaplan" wrote:

Quote:
Use the HttpContext.SkipAuthorization property to turn authorization on or
off programmatically on a page by page basis. You probably want to put this
code in global.asax or an IHttpModule.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:A9894367-B2BC-496D-9FD7-057381022AC6 (AT) microsoft (DOT) com...
Hi

I am trying to bypass Forms Authentication on certain pages
programmatically. Any thoughts will be appreciated.

Thanks,
AJ




Reply With Quote
  #4  
Old   
Dominick Baier
 
Posts: n/a

Default Re: How to bypass Forms Authentication on selected pages programma - 02-13-2007 , 02:54 PM



you have to set SkipAuthorization to true

HttpContext.Current.SkipAuthorization = true;

-----
Dominick Baier (http://www.leastprivilege.com)

Developing More Secure Microsoft ASP.NET 2.0 Applications (http://www.microsoft.com/mspress/books/9989.asp)

Quote:
Hey Joe, thanks for the last post.

I am using the following code in Global.asax:
Private Sub Global_AuthenticateRequest(ByVal sender As Object,
ByVal e
As System.EventArgs) Handles MyBase.AuthenticateRequest
Dim instance As HttpContext
If Request.Path = "/TestProject/FileUpload.aspx" Then
instance.SkipAuthorization = False
End If
End Sub
I know what you said seems very staright forward. But it hasn't worked
in my case yet. I know I am missing something somewhere. I have tried
this in Application_AuthenticateRequest as well. Let me know

Appreciate your help,
AJ
"Joe Kaplan" wrote:
Not the query string, but the Request.Url or Request.Path property.
I don't really have a sample for you, but basically your code would
do this:

In the appropriate event (probably the Authenticate event so this
runs after authentication but before authorization) check the Url of
the Request to see if it matches one of the resources you want to
exclude. If so, set SkipAuthorization to false. Be very careful
with how you do the matching of the path against your list of
exclusions. There isn't really much to it. Just play around with it.


There are also probably some fancier ways you can do this. You might
apply some kind of marker to the actual page via a base class, marker
interface or custom attribute on your pages and determine that from
the IHttpHandler that is set up in the HttpContext for the request.
I haven't tried that, but I don't see why it wouldn't work. Part of
it depends on how you want to maintain the list of excluded
resources. If you want to do this from the code in the page, I'd
take this approach. If you want to maintain a list of their URLs,
then the previous approach is better. However, that kind of thing
might be easier to deal with through the standard location tags in
web.config.

I'm curious if Dominick (or anyone else) sees this thread and has a
strong opinion about this.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:7E76E7BF-60DC-441D-9A43-841CBBE0087E (AT) microsoft (DOT) com...
Thanks Joe.

Do you have an example of this property being used in Global.asax? I
am
not
sure about how to check to see if -- this is the right page to be
left
out
for authentication.
Should I use a QueryString for this check?

Thanks again
AJ
"Joe Kaplan" wrote:

Use the HttpContext.SkipAuthorization property to turn
authorization on
or
off programmatically on a page by page basis. You probably want to
put
this
code in global.asax or an IHttpModule.
Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:A9894367-B2BC-496D-9FD7-057381022AC6 (AT) microsoft (DOT) com...
Hi

I am trying to bypass Forms Authentication on certain pages
programmatically. Any thoughts will be appreciated.

Thanks,
AJ



Reply With Quote
  #5  
Old   
Joe Kaplan
 
Posts: n/a

Default Re: How to bypass Forms Authentication on selected pages programma - 02-13-2007 , 02:58 PM



Not the query string, but the Request.Url or Request.Path property. I don't
really have a sample for you, but basically your code would do this:

In the appropriate event (probably the Authenticate event so this runs after
authentication but before authorization) check the Url of the Request to see
if it matches one of the resources you want to exclude. If so, set
SkipAuthorization to false. Be very careful with how you do the matching of
the path against your list of exclusions. There isn't really much to it.
Just play around with it.

There are also probably some fancier ways you can do this. You might apply
some kind of marker to the actual page via a base class, marker interface or
custom attribute on your pages and determine that from the IHttpHandler that
is set up in the HttpContext for the request. I haven't tried that, but I
don't see why it wouldn't work. Part of it depends on how you want to
maintain the list of excluded resources. If you want to do this from the
code in the page, I'd take this approach. If you want to maintain a list of
their URLs, then the previous approach is better. However, that kind of
thing might be easier to deal with through the standard location tags in
web.config.

I'm curious if Dominick (or anyone else) sees this thread and has a strong
opinion about this.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote

Quote:
Thanks Joe.

Do you have an example of this property being used in Global.asax? I am
not
sure about how to check to see if -- this is the right page to be left
out
for authentication.

Should I use a QueryString for this check?


Thanks again
AJ

"Joe Kaplan" wrote:

Use the HttpContext.SkipAuthorization property to turn authorization on
or
off programmatically on a page by page basis. You probably want to put
this
code in global.asax or an IHttpModule.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:A9894367-B2BC-496D-9FD7-057381022AC6 (AT) microsoft (DOT) com...
Hi

I am trying to bypass Forms Authentication on certain pages
programmatically. Any thoughts will be appreciated.

Thanks,
AJ






Reply With Quote
  #6  
Old   
ajmehra
 
Posts: n/a

Default Re: How to bypass Forms Authentication on selected pages programma - 02-13-2007 , 03:50 PM



Hey Joe, thanks for the last post.

I am using the following code in Global.asax:
Private Sub Global_AuthenticateRequest(ByVal sender As Object, ByVal e
As System.EventArgs) Handles MyBase.AuthenticateRequest
Dim instance As HttpContext
If Request.Path = "/TestProject/FileUpload.aspx" Then
instance.SkipAuthorization = False
End If
End Sub

I know what you said seems very staright forward. But it hasn't worked in my
case yet. I know I am missing something somewhere. I have tried this in
Application_AuthenticateRequest as well. Let me know

Appreciate your help,
AJ
"Joe Kaplan" wrote:

Quote:
Not the query string, but the Request.Url or Request.Path property. I don't
really have a sample for you, but basically your code would do this:

In the appropriate event (probably the Authenticate event so this runs after
authentication but before authorization) check the Url of the Request to see
if it matches one of the resources you want to exclude. If so, set
SkipAuthorization to false. Be very careful with how you do the matching of
the path against your list of exclusions. There isn't really much to it.
Just play around with it.

There are also probably some fancier ways you can do this. You might apply
some kind of marker to the actual page via a base class, marker interface or
custom attribute on your pages and determine that from the IHttpHandler that
is set up in the HttpContext for the request. I haven't tried that, but I
don't see why it wouldn't work. Part of it depends on how you want to
maintain the list of excluded resources. If you want to do this from the
code in the page, I'd take this approach. If you want to maintain a list of
their URLs, then the previous approach is better. However, that kind of
thing might be easier to deal with through the standard location tags in
web.config.

I'm curious if Dominick (or anyone else) sees this thread and has a strong
opinion about this.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:7E76E7BF-60DC-441D-9A43-841CBBE0087E (AT) microsoft (DOT) com...
Thanks Joe.

Do you have an example of this property being used in Global.asax? I am
not
sure about how to check to see if -- this is the right page to be left
out
for authentication.

Should I use a QueryString for this check?


Thanks again
AJ

"Joe Kaplan" wrote:

Use the HttpContext.SkipAuthorization property to turn authorization on
or
off programmatically on a page by page basis. You probably want to put
this
code in global.asax or an IHttpModule.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:A9894367-B2BC-496D-9FD7-057381022AC6 (AT) microsoft (DOT) com...
Hi

I am trying to bypass Forms Authentication on certain pages
programmatically. Any thoughts will be appreciated.

Thanks,
AJ







Reply With Quote
  #7  
Old   
ajmehra
 
Posts: n/a

Default Re: How to bypass Forms Authentication on selected pages programma - 02-13-2007 , 04:09 PM



Hey Dominick,

That is not working either.

Thanks,
AJ

"Dominick Baier" wrote:

Quote:
you have to set SkipAuthorization to true

HttpContext.Current.SkipAuthorization = true;

-----
Dominick Baier (http://www.leastprivilege.com)

Developing More Secure Microsoft ASP.NET 2.0 Applications (http://www.microsoft.com/mspress/books/9989.asp)

Hey Joe, thanks for the last post.

I am using the following code in Global.asax:
Private Sub Global_AuthenticateRequest(ByVal sender As Object,
ByVal e
As System.EventArgs) Handles MyBase.AuthenticateRequest
Dim instance As HttpContext
If Request.Path = "/TestProject/FileUpload.aspx" Then
instance.SkipAuthorization = False
End If
End Sub
I know what you said seems very staright forward. But it hasn't worked
in my case yet. I know I am missing something somewhere. I have tried
this in Application_AuthenticateRequest as well. Let me know

Appreciate your help,
AJ
"Joe Kaplan" wrote:
Not the query string, but the Request.Url or Request.Path property.
I don't really have a sample for you, but basically your code would
do this:

In the appropriate event (probably the Authenticate event so this
runs after authentication but before authorization) check the Url of
the Request to see if it matches one of the resources you want to
exclude. If so, set SkipAuthorization to false. Be very careful
with how you do the matching of the path against your list of
exclusions. There isn't really much to it. Just play around with it.


There are also probably some fancier ways you can do this. You might
apply some kind of marker to the actual page via a base class, marker
interface or custom attribute on your pages and determine that from
the IHttpHandler that is set up in the HttpContext for the request.
I haven't tried that, but I don't see why it wouldn't work. Part of
it depends on how you want to maintain the list of excluded
resources. If you want to do this from the code in the page, I'd
take this approach. If you want to maintain a list of their URLs,
then the previous approach is better. However, that kind of thing
might be easier to deal with through the standard location tags in
web.config.

I'm curious if Dominick (or anyone else) sees this thread and has a
strong opinion about this.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:7E76E7BF-60DC-441D-9A43-841CBBE0087E (AT) microsoft (DOT) com...
Thanks Joe.

Do you have an example of this property being used in Global.asax? I
am
not
sure about how to check to see if -- this is the right page to be
left
out
for authentication.
Should I use a QueryString for this check?

Thanks again
AJ
"Joe Kaplan" wrote:

Use the HttpContext.SkipAuthorization property to turn
authorization on
or
off programmatically on a page by page basis. You probably want to
put
this
code in global.asax or an IHttpModule.
Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:A9894367-B2BC-496D-9FD7-057381022AC6 (AT) microsoft (DOT) com...
Hi

I am trying to bypass Forms Authentication on certain pages
programmatically. Any thoughts will be appreciated.

Thanks,
AJ




Reply With Quote
  #8  
Old   
Joe Kaplan
 
Posts: n/a

Default Re: How to bypass Forms Authentication on selected pages programma - 02-13-2007 , 05:10 PM



Which part isn't working? Is your If condition not matching or is the
SkipAuthorization actually not working. Dominick is definitely right, it
has to be set to true.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote

Quote:
Hey Dominick,

That is not working either.

Thanks,
AJ

"Dominick Baier" wrote:

you have to set SkipAuthorization to true

HttpContext.Current.SkipAuthorization = true;

-----
Dominick Baier (http://www.leastprivilege.com)

Developing More Secure Microsoft ASP.NET 2.0 Applications
(http://www.microsoft.com/mspress/books/9989.asp)

Hey Joe, thanks for the last post.

I am using the following code in Global.asax:
Private Sub Global_AuthenticateRequest(ByVal sender As Object,
ByVal e
As System.EventArgs) Handles MyBase.AuthenticateRequest
Dim instance As HttpContext
If Request.Path = "/TestProject/FileUpload.aspx" Then
instance.SkipAuthorization = False
End If
End Sub
I know what you said seems very staright forward. But it hasn't worked
in my case yet. I know I am missing something somewhere. I have tried
this in Application_AuthenticateRequest as well. Let me know

Appreciate your help,
AJ
"Joe Kaplan" wrote:
Not the query string, but the Request.Url or Request.Path property.
I don't really have a sample for you, but basically your code would
do this:

In the appropriate event (probably the Authenticate event so this
runs after authentication but before authorization) check the Url of
the Request to see if it matches one of the resources you want to
exclude. If so, set SkipAuthorization to false. Be very careful
with how you do the matching of the path against your list of
exclusions. There isn't really much to it. Just play around with it.


There are also probably some fancier ways you can do this. You might
apply some kind of marker to the actual page via a base class, marker
interface or custom attribute on your pages and determine that from
the IHttpHandler that is set up in the HttpContext for the request.
I haven't tried that, but I don't see why it wouldn't work. Part of
it depends on how you want to maintain the list of excluded
resources. If you want to do this from the code in the page, I'd
take this approach. If you want to maintain a list of their URLs,
then the previous approach is better. However, that kind of thing
might be easier to deal with through the standard location tags in
web.config.

I'm curious if Dominick (or anyone else) sees this thread and has a
strong opinion about this.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:7E76E7BF-60DC-441D-9A43-841CBBE0087E (AT) microsoft (DOT) com...
Thanks Joe.

Do you have an example of this property being used in Global.asax? I
am
not
sure about how to check to see if -- this is the right page to be
left
out
for authentication.
Should I use a QueryString for this check?

Thanks again
AJ
"Joe Kaplan" wrote:

Use the HttpContext.SkipAuthorization property to turn
authorization on
or
off programmatically on a page by page basis. You probably want to
put
this
code in global.asax or an IHttpModule.
Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:A9894367-B2BC-496D-9FD7-057381022AC6 (AT) microsoft (DOT) com...
Hi

I am trying to bypass Forms Authentication on certain pages
programmatically. Any thoughts will be appreciated.

Thanks,
AJ






Reply With Quote
  #9  
Old   
ajmehra
 
Posts: n/a

Default Re: How to bypass Forms Authentication on selected pages programma - 02-13-2007 , 05:41 PM



Hey Joe,
I am not sure which part isn't working.
here's the code I am using in Global_AuthenticateRequest event in global.asax.
If Request.Path = "/TestProject/fileupload.aspx" Then
HttpContext.Current.SkipAuthorization = True
End If

and the URL I am trying to get to without a cookie is
http://localhost/TestProject/fileupload.aspx
but I am getting redirected to the login page each time.
am I missing a setting somewhere?

Thanks,
Aj

"Joe Kaplan" wrote:

Quote:
Which part isn't working? Is your If condition not matching or is the
SkipAuthorization actually not working. Dominick is definitely right, it
has to be set to true.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:B2C9EC52-4B8D-4270-B0ED-87D29B548F29 (AT) microsoft (DOT) com...
Hey Dominick,

That is not working either.

Thanks,
AJ

"Dominick Baier" wrote:

you have to set SkipAuthorization to true

HttpContext.Current.SkipAuthorization = true;

-----
Dominick Baier (http://www.leastprivilege.com)

Developing More Secure Microsoft ASP.NET 2.0 Applications
(http://www.microsoft.com/mspress/books/9989.asp)

Hey Joe, thanks for the last post.

I am using the following code in Global.asax:
Private Sub Global_AuthenticateRequest(ByVal sender As Object,
ByVal e
As System.EventArgs) Handles MyBase.AuthenticateRequest
Dim instance As HttpContext
If Request.Path = "/TestProject/FileUpload.aspx" Then
instance.SkipAuthorization = False
End If
End Sub
I know what you said seems very staright forward. But it hasn't worked
in my case yet. I know I am missing something somewhere. I have tried
this in Application_AuthenticateRequest as well. Let me know

Appreciate your help,
AJ
"Joe Kaplan" wrote:
Not the query string, but the Request.Url or Request.Path property.
I don't really have a sample for you, but basically your code would
do this:

In the appropriate event (probably the Authenticate event so this
runs after authentication but before authorization) check the Url of
the Request to see if it matches one of the resources you want to
exclude. If so, set SkipAuthorization to false. Be very careful
with how you do the matching of the path against your list of
exclusions. There isn't really much to it. Just play around with it.


There are also probably some fancier ways you can do this. You might
apply some kind of marker to the actual page via a base class, marker
interface or custom attribute on your pages and determine that from
the IHttpHandler that is set up in the HttpContext for the request.
I haven't tried that, but I don't see why it wouldn't work. Part of
it depends on how you want to maintain the list of excluded
resources. If you want to do this from the code in the page, I'd
take this approach. If you want to maintain a list of their URLs,
then the previous approach is better. However, that kind of thing
might be easier to deal with through the standard location tags in
web.config.

I'm curious if Dominick (or anyone else) sees this thread and has a
strong opinion about this.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:7E76E7BF-60DC-441D-9A43-841CBBE0087E (AT) microsoft (DOT) com...
Thanks Joe.

Do you have an example of this property being used in Global.asax? I
am
not
sure about how to check to see if -- this is the right page to be
left
out
for authentication.
Should I use a QueryString for this check?

Thanks again
AJ
"Joe Kaplan" wrote:

Use the HttpContext.SkipAuthorization property to turn
authorization on
or
off programmatically on a page by page basis. You probably want to
put
this
code in global.asax or an IHttpModule.
Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:A9894367-B2BC-496D-9FD7-057381022AC6 (AT) microsoft (DOT) com...
Hi

I am trying to bypass Forms Authentication on certain pages
programmatically. Any thoughts will be appreciated.

Thanks,
AJ







Reply With Quote
  #10  
Old   
ajmehra
 
Posts: n/a

Default Re: How to bypass Forms Authentication on selected pages programma - 02-13-2007 , 05:57 PM



Hey Joe,

I tried setting this:
HttpContext.Current.SkipAuthorization = True

without any condition, basically for every page. but I am still getting
redirected to the login page. can I set this property somewhere else?
Thanks,
AJ

"Joe Kaplan" wrote:

Quote:
Which part isn't working? Is your If condition not matching or is the
SkipAuthorization actually not working. Dominick is definitely right, it
has to be set to true.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:B2C9EC52-4B8D-4270-B0ED-87D29B548F29 (AT) microsoft (DOT) com...
Hey Dominick,

That is not working either.

Thanks,
AJ

"Dominick Baier" wrote:

you have to set SkipAuthorization to true

HttpContext.Current.SkipAuthorization = true;

-----
Dominick Baier (http://www.leastprivilege.com)

Developing More Secure Microsoft ASP.NET 2.0 Applications
(http://www.microsoft.com/mspress/books/9989.asp)

Hey Joe, thanks for the last post.

I am using the following code in Global.asax:
Private Sub Global_AuthenticateRequest(ByVal sender As Object,
ByVal e
As System.EventArgs) Handles MyBase.AuthenticateRequest
Dim instance As HttpContext
If Request.Path = "/TestProject/FileUpload.aspx" Then
instance.SkipAuthorization = False
End If
End Sub
I know what you said seems very staright forward. But it hasn't worked
in my case yet. I know I am missing something somewhere. I have tried
this in Application_AuthenticateRequest as well. Let me know

Appreciate your help,
AJ
"Joe Kaplan" wrote:
Not the query string, but the Request.Url or Request.Path property.
I don't really have a sample for you, but basically your code would
do this:

In the appropriate event (probably the Authenticate event so this
runs after authentication but before authorization) check the Url of
the Request to see if it matches one of the resources you want to
exclude. If so, set SkipAuthorization to false. Be very careful
with how you do the matching of the path against your list of
exclusions. There isn't really much to it. Just play around with it.


There are also probably some fancier ways you can do this. You might
apply some kind of marker to the actual page via a base class, marker
interface or custom attribute on your pages and determine that from
the IHttpHandler that is set up in the HttpContext for the request.
I haven't tried that, but I don't see why it wouldn't work. Part of
it depends on how you want to maintain the list of excluded
resources. If you want to do this from the code in the page, I'd
take this approach. If you want to maintain a list of their URLs,
then the previous approach is better. However, that kind of thing
might be easier to deal with through the standard location tags in
web.config.

I'm curious if Dominick (or anyone else) sees this thread and has a
strong opinion about this.

Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:7E76E7BF-60DC-441D-9A43-841CBBE0087E (AT) microsoft (DOT) com...
Thanks Joe.

Do you have an example of this property being used in Global.asax? I
am
not
sure about how to check to see if -- this is the right page to be
left
out
for authentication.
Should I use a QueryString for this check?

Thanks again
AJ
"Joe Kaplan" wrote:

Use the HttpContext.SkipAuthorization property to turn
authorization on
or
off programmatically on a page by page basis. You probably want to
put
this
code in global.asax or an IHttpModule.
Joe K.

--
Joe Kaplan-MS MVP Directory Services Programming
Co-author of "The .NET Developer's Guide to Directory Services
Programming"
http://www.directoryprogramming.net
--
"ajmehra" <ajmehra (AT) discussions (DOT) microsoft.com> wrote in message
news:A9894367-B2BC-496D-9FD7-057381022AC6 (AT) microsoft (DOT) com...
Hi

I am trying to bypass Forms Authentication on certain pages
programmatically. Any thoughts will be appreciated.

Thanks,
AJ







Reply With Quote
Reply




Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.4
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.