<authorization> Issue RSS

• • Reply
  

  senior_oracl...

  Member

  30 Points

  163 Posts

  <authorization> Issue

  Oct 12, 2011 08:00 AM|LINK

  I have created a custom Login Page named login.aspx , and everything is working fine in the web.config I changed the authentication mode to :

  <authentication mode="Forms"/> , I added the :

  <authorization>

        <deny users ="?" />

        </authorization> to the web.config , when I tested the script by trying to display a page that requires authentication I was redirected to the login page but all the images are not displayed , so I added :

  <location path="images">
  <system.web>
  <authorization>
  <allow users ="*" />
  </authorization>
  </system.web>
  </location>

  and tested again , I have the login page displayed correctly , but now when I enter the user name and the password and click the submit button , I am still in the same page im not redirected to the Reports.aspx any help please ?

   

  code is available for both login page and web.config if you want

• • Reply
  

  sukumarraju

  All-Star

  16931 Points

  2999 Posts

  Re: <authorization> Issue

  Oct 12, 2011 01:56 PM|LINK

  senior_oracle

  <deny users ="?" />

  Refer http://weblogs.asp.net/gurusarkar/archive/2008/09/29/setting-authorization-rules-for-a-particular-page-or-folder-in-web-config.aspx

  -- "Mark As Answer" if my reply helped you --
  Application Architecture Guide 2.0
  My Blog
  Twitter
• • Reply
  

  sukumarraju

  All-Star

  16931 Points

  2999 Posts

  Re: <authorization> Issue

  Oct 12, 2011 02:00 PM|LINK

  senior_oracle

  login page and web.config

  Post it here please.

  Have you set DefaultPage in Web.config or redirecting from Login page upon succeessful log in?

  <authentication mode="Forms">
   <forms defaultUrl="Default.aspx" timeout="1440" slidingExpiration="true" />
  </authentication>

  -- "Mark As Answer" if my reply helped you --
  Application Architecture Guide 2.0
  My Blog
  Twitter
• • Reply
  

  senior_oracl...

  Member

  30 Points

  163 Posts

  Re: <authorization> Issue

  Oct 12, 2011 02:10 PM|LINK

  I have seen the link I did use this logic , but still having the same problem any way this is my web.config below , all i need is to restrict access to anonymos users and when a user enters his correct credentials he should be redirected to a page called secure.aspx

   

  <?xml version="1.0" encoding="UTF-8"?>
  <!--
      Note: As an alternative to hand editing this file you can use the
      web admin tool to configure settings for your application. Use
      the Website->Asp.Net Configuration option in Visual Studio.
      A full list of settings and comments can be found in
      machine.config.comments usually located in
      \Windows\Microsoft.Net\Framework\v2.x\Config
  -->
  <configuration>
   <configSections>
    <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
     <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
      <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
      <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
       <section name="jsonSerialization" type="System.Web.Configuration.ScriptingJsonSerializationSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="Everywhere" />
       <section name="profileService" type="System.Web.Configuration.ScriptingProfileServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
       <section name="authenticationService" type="System.Web.Configuration.ScriptingAuthenticationServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
       <section name="roleService" type="System.Web.Configuration.ScriptingRoleServiceSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" />
      </sectionGroup>
     </sectionGroup>
    </sectionGroup>
   </configSections>
   <appSettings />
   <system.web>
    <!--
              Set compilation debug="true" to insert debugging
              symbols into the compiled page. Because this
              affects performance, set this value to true only
              during development.
          -->
    <roleManager defaultProvider="AspNetWindowsTokenRoleProvider" />
    
    <compilation debug="true">
     <assemblies>
      <add assembly="System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
      <add assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      <add assembly="System.Data.DataSetExtensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
      <add assembly="System.Xml.Linq, Version=3.5.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
     </assemblies>
    </compilation>
    <!--
              The <authentication> section enables configuration
              of the security authentication mode used by
              ASP.NET to identify an incoming user.
          -->
    <authentication mode="Forms" />
   
     
      <!--
              The <customErrors> section enables configuration
              of what to do if/when an unhandled error occurs
              during the execution of a request. Specifically,
              it enables developers to configure html error pages
              to be displayed in place of a error stack trace.

          <customErrors mode="RemoteOnly" defaultRedirect="GenericErrorPage.htm">
              <error statusCode="403" redirect="NoAccess.htm" />
              <error statusCode="404" redirect="FileNotFound.htm" />
          </customErrors>
          -->
    <pages>
     <controls>
      <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
      <add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
     </controls>
    </pages>
    <httpHandlers>
     <remove verb="*" path="*.asmx" />
     <add verb="*" path="*.asmx" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
     <add verb="*" path="*_AppService.axd" validate="false" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
     <add verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" validate="false" />
    </httpHandlers>
    <httpModules>
     <add name="ScriptModule" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
    </httpModules>

      <authorization>

        <deny users="?" />
        </authorization>
       

    </system.web>
   <system.codedom>
    <compilers>
     <compiler language="c#;cs;csharp" extension=".cs" warningLevel="4" type="Microsoft.CSharp.CSharpCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
      <providerOption name="CompilerVersion" value="v3.5" />
      <providerOption name="WarnAsError" value="false" />
     </compiler>
     <compiler language="vb;vbs;visualbasic;vbscript" extension=".vb" warningLevel="4" type="Microsoft.VisualBasic.VBCodeProvider, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089">
      <providerOption name="CompilerVersion" value="v3.5" />
      <providerOption name="OptionInfer" value="true" />
      <providerOption name="WarnAsError" value="false" />
     </compiler>
    </compilers>
   </system.codedom>
   <!--
          The system.webServer section is required for running ASP.NET AJAX under Internet
          Information Services 7.0.  It is not necessary for previous version of IIS.
      -->
   <system.webServer>
    <validation validateIntegratedModeConfiguration="false" />
    <modules>
     <remove name="ScriptModule" />
     <add name="ScriptModule" preCondition="managedHandler" type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
    </modules>
    <handlers>
     <remove name="WebServiceHandlerFactory-Integrated" />
     <remove name="ScriptHandlerFactory" />
     <remove name="ScriptHandlerFactoryAppServices" />
     <remove name="ScriptResource" />
     <add name="ScriptHandlerFactory" verb="*" path="*.asmx" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
     <add name="ScriptHandlerFactoryAppServices" verb="*" path="*_AppService.axd" preCondition="integratedMode" type="System.Web.Script.Services.ScriptHandlerFactory, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
     <add name="ScriptResource" preCondition="integratedMode" verb="GET,HEAD" path="ScriptResource.axd" type="System.Web.Handlers.ScriptResourceHandler, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
    </handlers>
          <defaultDocument>
              <files>
                  <add value="login.aspx" />
              </files>
          </defaultDocument>
   </system.webServer>
   <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
     <dependentAssembly>
      <assemblyIdentity name="System.Web.Extensions" publicKeyToken="31bf3856ad364e35" />
      <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
     </dependentAssembly>
     <dependentAssembly>
      <assemblyIdentity name="System.Web.Extensions.Design" publicKeyToken="31bf3856ad364e35" />
      <bindingRedirect oldVersion="1.0.0.0-1.1.0.0" newVersion="3.5.0.0" />
     </dependentAssembly>
    </assemblyBinding>
   </runtime>

    <location path="images">
      <system.web>
        <authorization>
          <allow users="*" />
        </authorization>
      </system.web>
    </location>
  </configuration>

   

• • Reply
  

  senior_oracl...

  Member

  30 Points

  163 Posts

  Re: <authorization> Issue

  Oct 12, 2011 02:24 PM|LINK

  And below is the login page :

   

  login.aspx.cs:

   

  using System;
  using System.Collections.Generic;
  using System.Linq;
  using System.Web;
  using System.Web.UI;
  using System.Web.UI.WebControls;
  using System.Data.SqlClient;
  public partial class login : System.Web.UI.Page
  {
      protected void Page_Load(object sender, EventArgs e)
      {

      }
    
      SqlConnection con = new SqlConnection("Data Source=.;Initial Catalog=onlineusers;Integrated Security=True");
      SqlCommand cmd;
      SqlDataReader dr;

      protected void Button1_Click(object sender, EventArgs e)
      {
         
      }
      protected void Button1_Click1(object sender, EventArgs e)
      {
          con.Open();
          cmd = new SqlCommand("Select Password from OnlineUsers where BBAID =' " + TextBox1.Text + "'", con);
          dr = cmd.ExecuteReader();
          if (!dr.Read())
          {

              Response.Write("No Details Provided");

   

          }
          else
          {
              if (dr[0].ToString() == TextBox2.Text)

                  Response.Redirect("secure.aspx");

              else

                  Response.Write("الرجاء ادخال كلمة المرور");
          }
      }
  }

• • Reply
  

  sukumarraju

  All-Star

  16931 Points

  2999 Posts

  Re: <authorization> Issue

  Oct 12, 2011 02:30 PM|LINK

  senior_oracle

  <authentication mode="Forms" />

  Update the above to, if still the same issue, provide your Login code behind.

  <authentication mode="Forms">
   <forms defaultUrl="secure.aspx" />
  </authentication>

  -- "Mark As Answer" if my reply helped you --
  Application Architecture Guide 2.0
  My Blog
  Twitter
• • Reply
  

  senior_oracl...

  Member

  30 Points

  163 Posts

  Re: <authorization> Issue

  Oct 12, 2011 02:36 PM|LINK

  i did update the code in the web.config and still having the same issue , please can you explain " Provide login code behind" ?

   

  I already posted the login code on the site if this is what you mean and if somethins else please tell me .

   

  thank you for your great support

   

  waiting your reply

• • Reply
  

  sukumarraju

  All-Star

  16931 Points

  2999 Posts

  Re: <authorization> Issue

  Oct 12, 2011 02:40 PM|LINK

  Authenticating the user against SQL Server database without ASP.NET Membership API is discussed here number of times...

  Refer http://forums.asp.net/t/1250726.aspx

  Debug the source and let us know the outcome. Make sure that you escape white spaces while reading username and password from TextBox controls i.e., String.Trim()

  -- "Mark As Answer" if my reply helped you --
  Application Architecture Guide 2.0
  My Blog
  Twitter
  • Marked as answer by Hua-Jun Li - MSFT on Oct 18, 2011 08:56 AM