| Groups | Blog | Home |
asp.net security : role/group authorization not recognizing user groups.
I've seen other posts that seem to have a similar problem but none
with a posted solution, so here goes again.. My application does not allow anonymous access, and integrated windows authentication is enabled. In my web config I have the following: <authentication mode="Windows"/> <authorization> <allow roles="ie.mydomain\EDI_GROUP,ie.mydomain\EDI_OPS"/> <deny users="*"/> </authorization> <identity impersonate="true"/> As far as I can tell this should be all I need. However users who are members of the domain groups EDI_GROUP or EDI_OPS get access denied for the default.aspx page (in application root directory). I have verified the users are members of the groups and that host is aware of the groups ( double checked by restarting the server.. twice!). Interesting, within the application I can programatically identify the users as members of the groups but only if I use: WindowsPrincipal principal = new WindowsPrincipal(WindowsIdentity.GetCurrent()); bool memberOfEDI_Ops = principal.IsInRole("EDI_Ops"); If I try to use : IPrincipal principal = Thread.CurrentPrincipal; bool memberOfEDI_Ops = principal.IsInRole("EDI_Ops"); memberOfEDI_Ops will be false ( further investigation revealed that the IPrincipal here was in fact a GenericPrincipal and not the required WindowsPrincipal). This may be a red herring but the second approach will in fact return a WindowsPrincipal when running on the devstudio web server on my development machine. My development machine is an XP SP2 machine and the IIS server is a 2003 machine with SP1. Any Ideas, suggestions?
It is strange that your Thread.CurrentPrincipal isn't a WindowsPrincipal.
What is the Context.User property in this case? Thread.CurrentPrincipal and Context.User should be the same in an ASP.NET app in most circumstances. 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 -- [quoted text, click to view] "TygerKrash" <dave.mcgowan@gmail.com> wrote in message news:1194352514.662852.295560@57g2000hsv.googlegroups.com... > I've seen other posts that seem to have a similar problem but none > with a posted solution, so here goes again.. > > My application does not allow anonymous access, and integrated windows > authentication is enabled. > > In my web config I have the following: > > <authentication mode="Windows"/> > <authorization> > <allow roles="ie.mydomain\EDI_GROUP,ie.mydomain\EDI_OPS"/> > <deny users="*"/> > </authorization> > <identity impersonate="true"/> > > As far as I can tell this should be all I need. > > > However users who are members of the domain groups EDI_GROUP or > EDI_OPS get access denied for the default.aspx page (in application > root directory). > > > I have verified the users are members of the groups and that host is > aware of the groups ( double checked by restarting the server.. > twice!). > > Interesting, within the application I can programatically identify the > users as members of the groups but only if I use: > > WindowsPrincipal principal = new > WindowsPrincipal(WindowsIdentity.GetCurrent()); > bool memberOfEDI_Ops = principal.IsInRole("EDI_Ops"); > > If I try to use : > > IPrincipal principal = Thread.CurrentPrincipal; > bool memberOfEDI_Ops = principal.IsInRole("EDI_Ops"); > > memberOfEDI_Ops will be false ( further investigation revealed that > the IPrincipal here was in fact a GenericPrincipal and not the > required WindowsPrincipal). > > > This may be a red herring but the second approach will in fact return > a WindowsPrincipal when running on the devstudio web server on my > development machine. > > > My development machine is an XP SP2 machine and the IIS server is a > 2003 machine with SP1. > > Any Ideas, suggestions? >
If your app is using Windows security in IIS and web.config, the
authenticated user (Context.User) should be a WindowsPrincipal. Is it possible something else has been added to the stack like membership or something? I honestly don't know. 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 -- [quoted text, click to view] "TygerKrash" <dave.mcgowan@gmail.com> wrote in message news:1194888499.408333.159770@v2g2000hsf.googlegroups.com... > Hi Joe, > Thanks for the reply. > > I've just checked and Context.User is also appearing as a > GenericPrincipal (representing the same user). > > I can ,and given time constraints I probably will, just identify the > users role programatically and enforce my authorization that way, > so this isn't that serious a problem, but I am curious to get to the > bottom of this. > > > Dave. > > On Nov 10, 2:58 pm, "Joe Kaplan" > <joseph.e.kap...@removethis.accenture.com> wrote: >> It is strange that your Thread.CurrentPrincipal isn't a WindowsPrincipal. >> What is the Context.User property in this case? Thread.CurrentPrincipal >> and >> Context.User should be the same in an ASP.NET app in most circumstances. >> >> 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 >> --"TygerKrash" <dave.mcgo...@gmail.com> wrote in message >> >> news:1194352514.662852.295560@57g2000hsv.googlegroups.com... >> >> > I've seen other posts that seem to have a similar problem but none >> > with a posted solution, so here goes again.. >> >> > My application does not allow anonymous access, and integrated windows >> > authentication is enabled. >> >> > In my web config I have the following: >> >> > <authentication mode="Windows"/> >> > <authorization> >> > <allow roles="ie.mydomain\EDI_GROUP,ie.mydomain\EDI_OPS"/> >> > <deny users="*"/> >> > </authorization> >> > <identity impersonate="true"/> >> >> > As far as I can tell this should be all I need. >> >> > However users who are members of the domain groups EDI_GROUP or >> > EDI_OPS get access denied for the default.aspx page (in application >> > root directory). >> >> > I have verified the users are members of the groups and that host is >> > aware of the groups ( double checked by restarting the server.. >> > twice!). >> >> > Interesting, within the application I can programatically identify the >> > users as members of the groups but only if I use: >> >> > WindowsPrincipal principal = new >> > WindowsPrincipal(WindowsIdentity.GetCurrent()); >> > bool memberOfEDI_Ops = principal.IsInRole("EDI_Ops"); >> >> > If I try to use : >> >> > IPrincipal principal = Thread.CurrentPrincipal; >> > bool memberOfEDI_Ops = principal.IsInRole("EDI_Ops"); >> >> > memberOfEDI_Ops will be false ( further investigation revealed that >> > the IPrincipal here was in fact a GenericPrincipal and not the >> > required WindowsPrincipal). >> >> > This may be a red herring but the second approach will in fact return >> > a WindowsPrincipal when running on the devstudio web server on my >> > development machine. >> >> > My development machine is an XP SP2 machine and the IIS server is a >> > 2003 machine with SP1. >> >> > Any Ideas, suggestions? > >
Hi Joe,
Thanks for the reply. I've just checked and Context.User is also appearing as a GenericPrincipal (representing the same user). I can ,and given time constraints I probably will, just identify the users role programatically and enforce my authorization that way, so this isn't that serious a problem, but I am curious to get to the bottom of this. Dave. On Nov 10, 2:58 pm, "Joe Kaplan" [quoted text, click to view] <joseph.e.kap...@removethis.accenture.com> wrote: > It is strange that your Thread.CurrentPrincipal isn't a WindowsPrincipal. > What is the Context.User property in this case? Thread.CurrentPrincipal and > Context.User should be the same in an ASP.NET app in most circumstances. > > 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 > --"TygerKrash" <dave.mcgo...@gmail.com> wrote in message > > news:1194352514.662852.295560@57g2000hsv.googlegroups.com... > > > I've seen other posts that seem to have a similar problem but none > > with a posted solution, so here goes again.. > > > My application does not allow anonymous access, and integrated windows > > authentication is enabled. > > > In my web config I have the following: > > > <authentication mode="Windows"/> > > <authorization> > > <allow roles="ie.mydomain\EDI_GROUP,ie.mydomain\EDI_OPS"/> > > <deny users="*"/> > > </authorization> > > <identity impersonate="true"/> > > > As far as I can tell this should be all I need. > > > However users who are members of the domain groups EDI_GROUP or > > EDI_OPS get access denied for the default.aspx page (in application > > root directory). > > > I have verified the users are members of the groups and that host is > > aware of the groups ( double checked by restarting the server.. > > twice!). > > > Interesting, within the application I can programatically identify the > > users as members of the groups but only if I use: > > > WindowsPrincipal principal = new > > WindowsPrincipal(WindowsIdentity.GetCurrent()); > > bool memberOfEDI_Ops = principal.IsInRole("EDI_Ops"); > > > If I try to use : > > > IPrincipal principal = Thread.CurrentPrincipal; > > bool memberOfEDI_Ops = principal.IsInRole("EDI_Ops"); > > > memberOfEDI_Ops will be false ( further investigation revealed that > > the IPrincipal here was in fact a GenericPrincipal and not the > > required WindowsPrincipal). > > > This may be a red herring but the second approach will in fact return > > a WindowsPrincipal when running on the devstudio web server on my > > development machine. > > > My development machine is an XP SP2 machine and the IIS server is a > > 2003 machine with SP1. > > > Any Ideas, suggestions?
Theres no Membership entry in our application web config, maybe it's
something set in the machine.config but looking at that makes me kind of dizzy! Guess I'll mark this one up as 'weird' for the time being. I'll work around it and move on. thanks for your help. On Nov 12, 5:35 pm, "Joe Kaplan" [quoted text, click to view] <joseph.e.kap...@removethis.accenture.com> wrote: > If your app is using Windows security in IIS and web.config, the > authenticated user (Context.User) should be a WindowsPrincipal. Is it > possible something else has been added to the stack like membership or > something? I honestly don't know. > > 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 > --"TygerKrash" <dave.mcgo...@gmail.com> wrote in message > > news:1194888499.408333.159770@v2g2000hsf.googlegroups.com... > > > Hi Joe, > > Thanks for the reply. > > > I've just checked and Context.User is also appearing as a > > GenericPrincipal (representing the same user). > > > I can ,and given time constraints I probably will, just identify the > > users role programatically and enforce my authorization that way, > > so this isn't that serious a problem, but I am curious to get to the > > bottom of this. > > > Dave. > > > On Nov 10, 2:58 pm, "Joe Kaplan" > > <joseph.e.kap...@removethis.accenture.com> wrote: > >> It is strange that your Thread.CurrentPrincipal isn't a WindowsPrincipal. > >> What is the Context.User property in this case? Thread.CurrentPrincipal > >> and > >> Context.User should be the same in an ASP.NET app in most circumstances. > > >> 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 > >> --"TygerKrash" <dave.mcgo...@gmail.com> wrote in message > > >>news:1194352514.662852.295560@57g2000hsv.googlegroups.com... > > >> > I've seen other posts that seem to have a similar problem but none > >> > with a posted solution, so here goes again.. > > >> > My application does not allow anonymous access, and integrated windows > >> > authentication is enabled. > > >> > In my web config I have the following: > > >> > <authentication mode="Windows"/> > >> > <authorization> > >> > <allow roles="ie.mydomain\EDI_GROUP,ie.mydomain\EDI_OPS"/> > >> > <deny users="*"/> > >> > </authorization> > >> > <identity impersonate="true"/> > > >> > As far as I can tell this should be all I need. > > >> > However users who are members of the domain groups EDI_GROUP or > >> > EDI_OPS get access denied for the default.aspx page (in application > >> > root directory). > > >> > I have verified the users are members of the groups and that host is > >> > aware of the groups ( double checked by restarting the server.. > >> > twice!). > > >> > Interesting, within the application I can programatically identify the > >> > users as members of the groups but only if I use: > > >> > WindowsPrincipal principal = new > >> > WindowsPrincipal(WindowsIdentity.GetCurrent()); > >> > bool memberOfEDI_Ops = principal.IsInRole("EDI_Ops"); > > >> > If I try to use : > > >> > IPrincipal principal = Thread.CurrentPrincipal; > >> > bool memberOfEDI_Ops = principal.IsInRole("EDI_Ops"); > > >> > memberOfEDI_Ops will be false ( further investigation revealed that > >> > the IPrincipal here was in fact a GenericPrincipal and not the > >> > required WindowsPrincipal). > > >> > This may be a red herring but the second approach will in fact return > >> > a WindowsPrincipal when running on the devstudio web server on my > >> > development machine. > > >> > My development machine is an XP SP2 machine and the IIS server is a > >> > 2003 machine with SP1. > > >> > Any Ideas, suggestions?
Don't see what you're looking for? Try a search.
|
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |