[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2099
  • Last Modified:

WEB.CONFIG and IIS 6.0 Anonymous

Hello Gurus,

                   I am trying to find the most secure way to implement apps on our web server. I would like to know if you can use anonymous access in IIS and use the credentials in the web.config to authenticate. I have read where other developers just put a user account in IIS and turn off anonymous on the security tab??? I have pasted the code below that I am using in the web.config. Can anyone out there tell me the correct way to have an app authenticate.




<?xml version="1.0" encoding="utf-8" ?>
<configuration>

      <appSettings>
            <add key="keysConnString" value="Server=testserver;Database=Keys;uid=expert;pwd=exchange;" />
            <!--<add key="keyChainsConnString" value="Server=DLS-DEV-02\Development;Database=Keys;uid=sql;pwd=blank;" />
             <add key="keys" value="Server=testserver;Database=Keys;uid=sa;pwd=blank;" /> -->
            <add key="ErrorLogFile" value="~/ErrorLog.txt" />  <!-- create this file at the root of the app & give full control to everyone -->
            <!-- KeyChains.Systems.SystemId -->
            <add key="keysSystemId" value="1" />
            <add key="keysSystemId" value="2" />
            <!-- Urls, email servers -->
            <add key="SmtpServer" value="smtp.me.com" />
            <add key="keysDefaultPage" value="http://affiliatecorner.komen.org" />
            <add key="keysRegisterPage" value="/testing/Profile.aspx" />
            <add key="keysDefaultPage" value="/websites" />
            <add key="keysLoginDefaultPage" value="/Research" />
      </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="RemoteOnly" />

    <!--  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.
    -->
    <authentication mode="Windows" />


    <!--  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.
    -->
    <authorization>
        <allow users="*" /> <!-- Allow all users -->

            <!--  <allow     users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
                  <deny      users="[comma separated list of users]"
                             roles="[comma separated list of roles]"/>
            -->
    </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="100" 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".
    -->
   
    <!-- Original (default one) =
    <sessionState
            mode="InProc"
            stateConnectionString="tcpip=127.0.0.1:42424"
            sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes"
            cookieless="false"
            timeout="20"
    />
    -->
   
    <!--<sessionState
            mode="SQLServer"
            stateConnectionString="tcpip=127.0.0.1:42424"
            sqlConnectionString="data source=my-test-server\Development;uid=NT AD ACCOUNT;pwd=P@ssword;"
            cookieless="false"
            timeout="120"
      />-->
      
       <sessionState
            mode="SQLServer"
            stateConnectionString="tcpip=127.0.0.1:42424"
            sqlConnectionString="data source=my-test-server;uid=sa;pwd=blank;"
            cookieless="false"
            timeout="120"
      />
      
    <!--  GLOBALIZATION
          This section sets the globalization settings of the application.
    -->
    <globalization requestEncoding="utf-8" responseEncoding="utf-8" />
   
  </system.web>

</configuration>



0
SGKomen
Asked:
SGKomen
1 Solution
 
hendridmCommented:
Yes, you can disable anonymous access and then set permissions on the file level.  Then you should be able to pull the username who is logged in with Request.ServerVariables("HTTP_USER").

If you don't want to set file permissions, you can have your application do the authentication logic with Forms Authentication:
http://samples.gotdotnet.com/quickstart/aspplus/doc/formsauth.aspx
(For example, I use ASP.NET forms authentication to authenticate against Novell eDirectory)
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now