<authentication mode="Forms"> 
	<forms
		name=".IMSCookie" 
		loginUrl = "/login.aspx"
		protection = "All"
		path="/" />
	</authentication>

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

<script runat="server">

    Sub Page_Load

    End Sub
    
    Sub Button_Click( s As Object, e As EventArgs )
       lblMessage.Text = ""
       If IsValid Then
         If DBAuthenticate( txtUsername.Text, txtPassword.Text ) > 0 Then
           FormsAuthentication.RedirectFromLoginPage( txtUsername.Text, chkRemember.Checked )
         End If
       End If
    End Sub
    
    Function DBAuthenticate( strUsername As String, strPassword As String ) As Integer
       Dim conMyData As SqlConnection
       Dim cmdSelect As SqlCommand
       Dim parmReturnValue As SqlParameter
       Dim intResult As Integer
    
	'try and make a connection   
	Try
	       conMyData = New SqlConnection( ConfigurationSettings.AppSettings("strConn") )
	       cmdSelect = New SqlCommand( "DBAuthenticate", conMyData )
	       cmdSelect.CommandType = CommandType.StoredProcedure
	       parmReturnValue = cmdSelect.Parameters.Add( "RETURN_VALUE", SqlDbType.Int )
	       parmReturnValue.Direction = ParameterDirection.ReturnValue
	       cmdSelect.Parameters.Add( "@username", strUsername )
	       cmdSelect.Parameters.Add( "@password", strPassword )
	       conMyData.Open()
	       cmdSelect.ExecuteNonQuery()
	       intResult = cmdSelect.Parameters( "RETURN_VALUE" ).Value
       	'catch any exceptions that might be thrown
	Catch e as Exception
		Response.Write("An Error Occurred: " & e.toString())
	'clean up and close resources
	Finally
		conMyData.Close()
	End Try
			
       If intResult < 0 Then
         If intResult = -1 Then
           lblMessage.Text = "Username Not Registered!"
         Else
           lblMessage.Text = "Invalid Password!"
         End If
       End If
       Return intResult
    End Function

</script>

quote:

---

Originally posted by MichaelP

Do you have Default.aspx setup as the "default" page for your site?
In VS.Net, right click the Default.aspx page and select "Set as start page" and that should fix it methinks.

Michael

<Yoda>Use the Search page you must. Find the answer you will.</Yoda>

---

 <authorization>
   <deny users="?"/>
 </authorization>
</system.web>
  
   <!-- Allow all users to see Login.aspx -->
  <location path="Login.aspx">
     <system.web>
      <authorization>
        <allow users="*"/>
      </authorization>
     </system.web>
  </location>

quote:

---

Originally posted by MichaelP

What I posted was a cut and paste from a known working web.config file.
The </system.web> after the authorization was to show you that the next part went OUTSIDE of the system.web node.

Michael

<Yoda>Use the Search page you must. Find the answer you will.</Yoda>

---

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <!-- Custom Settings tailored for the IMS application
	   strConn = The Connection string
   -->
  <appSettings>
	<add key="strConn" value="User ID=IMS;Password=ibm123;Initial Catalog=IMS;Data Source=HERCULES;" />
  </appSettings> 
  <system.web>

    <!--  DYNAMIC DEBUG COMPILATION
          Set compilation debug="true" to insert debugging symbols (.pdb information)
          into the compiled page. Because this creates a larger file that executes
          more slowly, you should set this value to true only when debugging and to
          false at all other times. For more information, refer to the documentation about
          debugging ASP.NET files.
    -->
    <compilation defaultLanguage="vb" debug="true" />

    <!--  CUSTOM ERROR MESSAGES
          Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable. 
          Add <error> tags for each of the errors you want to handle.

          "On" Always display custom (friendly) messages.
          "Off" Always display detailed ASP.NET error information.
          "RemoteOnly" Display custom (friendly) messages only to users not running 
           on the local Web server. This setting is recommended for security purposes, so 
           that you do not display application detail information to remote clients.
    -->
    <customErrors mode="Off" />

    <!--  AUTHENTICATION 
          This section sets the authentication policies of the application. Possible modes are "Windows", 
          "Forms", "Passport" and "None"

          "None" No authentication is performed. 
          "Windows" IIS performs authentication (Basic, Digest, or Integrated Windows) according to 
           its settings for the application. Anonymous access must be disabled in IIS. 
          "Forms" You provide a custom form (Web page) for users to enter their credentials, and then 
           you authenticate them in your application. A user credential token is stored in a cookie.
          "Passport" Authentication is performed via a centralized authentication service provided
           by Microsoft that offers a single logon and core profile services for member sites.
    -->
    
    <!-- We use Forms authentication to deny anonymous users
		 only authenticated users allowed to use the application.
		 If the user is not authenticated he / she is directed to the
		 'login.aspx' page by using the loginUrl property of the forms tag.
	-->
    <authentication mode="Forms"> 
	<forms
		name=".IMSCookie" 
		loginUrl = "login.aspx"
		protection = "All"
		path="/" />
	</authentication>
	
    <!--  AUTHORIZATION 
          This section sets the authorization policies of the application. You can allow or deny access
          to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous 
          (unauthenticated) users. We DO NOT place an authorization tag in the web.config file on the root
          directory (this file) since we do not require end users to authenticate themselves to the files
          residing in this directory.
    -->
	<authorization>
        <deny users="?" />
	</authorization>


    <!--  APPLICATION-LEVEL TRACE LOGGING
          Application-level tracing enables trace log output for every page within an application. 
          Set trace enabled="true" to enable application trace logging.  If pageOutput="true", the
          trace information will be displayed at the bottom of each page.  Otherwise, you can view the 
          application trace log by browsing the "trace.axd" page from your web application
          root. 
    -->
    <trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true" />


    <!--  SESSION STATE SETTINGS
          By default ASP.NET uses cookies to identify which requests belong to a particular session. 
          If cookies are not available, a session can be tracked by adding a session identifier to the URL. 
          To disable cookies, set sessionState cookieless="true".
    -->
    <sessionState 
            mode="InProc"
            stateConnectionString="tcpip=127.0.0.1:42424"
            sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"
            cookieless="false" 
            timeout="20" 
    />

    <!--  GLOBALIZATION
          This section sets the globalization settings of the application. 
    -->
    <globalization requestEncoding="utf-8" responseEncoding="utf-8" />
   
  </system.web>
<!-- Allow all users to see Login.aspx -->
	<location path="login.aspx">
		<system.web>
			<authorization>
				<allow users="*" />
			</authorization>
		</system.web>
	</location>

</configuration>