allowDefinition='MachineToApplication'

Ask a Question related to ASP.NET Security, Design and Development.

  1. #1

    Default allowDefinition='MachineToApplication'

    My web application has the following structure

    RootFolder
    - file1.aspx
    - file2.aspx
    - web.config
    - admin_folder
    - protectedFile1.aspx
    - web.config

    RootFolder is setup as a Virtual Directory and has script only
    permissions.

    The web.config file under root is standard and grants access to
    everyone.
    The web.config file in admin_folder has forms authentication turned on
    denies access to all files. So when a user tries to access any file in
    the admin_folder, he should be promoted to login.

    Problem is when I access a protected page I get an error:

    Description: An error occurred during the processing of a
    configuration file required to service this request. Please review the
    specific error details below and modify your configuration file
    appropriately.

    Parser Error Message: It is an error to use a section registered as
    allowDefinition='MachineToApplication' beyond application level. This
    error can be caused by a virtual directory not being configured as an
    application in IIS.

    How should I be setting up the config files to allow free access to
    files under root and force login for files under admin_folder?
    Bijoy Naick Guest

  2. Similar Questions and Discussions

    1. web.config error... allowDefinition='MachineToApplication'
      This one just came out of the blue! One minute it is working and the next minute, it drops dead with the error below... ...
  3. #2

    Default RE: allowDefinition='MachineToApplication'

    Bijoy

    It appears that you have something in /admin_folder/web.config that is not allowed. More than likely you have an <authentication> section in the file. There are three options to solving this problem
    1. Remove the allowDefinition attribute from the <section> tag in machine.config. This may cause problems with the section you are using, so this is not recommended
    2. Remove the invalid section from /admin_folder/web.config. This is typically the best solution, but may cause additional work on your part
    3. Turn /admin_folder/ into it's own application within IIS. This is allows proper functionality of the invalid section, but may break your code

    David Banister
    David Banister Guest

Posting Permissions

  • You may not post new threads
  • You may post replies
  • You may not post attachments
  • You may not edit your posts

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139