Re: authorization problems

From: Jason Chiu (qysjc@yahoo.com.tw)
Date: 12/04/02


From: "Jason Chiu" <qysjc@yahoo.com.tw>
Date: Wed, 4 Dec 2002 16:09:43 +0800


I encounter the same problem.
When I use form authentication, the response.StateCode always 200 and
redirect to login page.
When I use Windows authentication, response.StateCode can get 401, So I
think it is BUG.

Maybe you can write a custom http module, and do urlauthorization yourself,
and attached it to the http modules pipeline.

"Sascha Ellerhoff" <sellerhoff@itbnet.de> ¼¶¼g©ó¶l¥ó·s»D
:#GX5TwrlCHA.2224@tkmsftngp02...
> hello newsgroup!
>
> I try to have a secure web. I use the asp.net security feature 'forms
> authentification' and the 'url authorization'
> forms authenfication does a correct job with cookies etc. But I think
> authorization caused problems.
>
> Situation:
> i have a public web site with secure subdirs.
>
> If a user choose one of the secure dirs the login.aspx will open. this is
> right.
> user with correct credentials and rights to enter the directory will
> redirect to the right website.
>
> problem:
> User with correct credentials but without rights do NOT get http 401
access
> denied message.
> (In MSDN of Microsoft it is descibed that user will get this error)
> Instead of this users will stay authenficated (but without autorization)
on
> login page with no information what happend.
>
> Question: Does the authorization act wrong? Has my configuration in
> web.config mistakes?
>
> web.config:
>
> <?xml version="1.0" encoding="utf-8" ?>
> <configuration>
> <system.web>
> <compilation defaultLanguage="vb" debug="true" />
> <customErrors mode="Off" />
> <globalization requestEncoding="utf-8" responseEncoding="utf-8" />
> <authentication mode="Forms">
> <forms path="/" name="WeckeAuth" loginUrl="login.aspx">
> <credentials passwordFormat="Clear">
> <user name="admin1" password="geheim" />
> <user name="admin2" password="geheim" />
> </credentials>
> </forms>
> </authentication>
> <authorization>
> <allow users="*" />
> </authorization>
> </system.web>
>
> <location path="admindir1">
> <system.web>
> <authorization>
> <allow users="admin1" />
> <deny users="*" />
> </authorization>
> </system.web>
> </location>
>
> <location path="admindir2">
> <system.web>
> <authorization>
> <allow users="admin2" />
> <deny users="*" />
> </authorization>
> </system.web>
> </location>
> </configuration>
>
>
>
> only admin1 has access zu admindir1
> only admin2 has access zu admindir2
>
> If admin2 use his credentials in admindir1 he does not get an error
message.
> he stay on login page.
>
> Does someone know my problem?
> Is the protection of the subdirs wrong?
>
>
> thx 4 help
> Sascha
>
>
>
>
>
>



Relevant Pages

  • Re: Default.aspx - newbie Q`
    ... check and redirect to the ReturnURL or Selected.aspx depending on the case. ... > and replace it with something that takes then straight to the login page. ... >> Curt Christianson ... >>> authentication ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Default.aspx - newbie Q`
    ... check and redirect to the ReturnURL or Selected.aspx depending on the case. ... > and replace it with something that takes then straight to the login page. ... >> Curt Christianson ... >>> authentication ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: ASP 2.0 Membership API
    ... After successful authentication, you want to redirect back to the original application, but the returnURL parameter contains only /App1 as the URL. ... The solution to that problem is adding a local login page to the application that does a manual redirect to the central authentication application. ... if not you have to use cookieless auth ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Detecting Failed Authorization
    ... after every authentication request and before the user ... is redirected to any login page. ... > "Ken Dopierala Jr." ... >> 'Redirect where you want the user to go. ...
    (microsoft.public.dotnet.framework.aspnet)
  • [Full-Disclosure] Advisory: Dark Age of Camelot - Weak encryption of network traffic exposed persona
    ... Weak encryption in game client exposed customer billing and authentication ... encryption for billing information. ... The login binary has undergone several updates since then. ...
    (Full-Disclosure)