# Setup: IIS 7.0 and above in Integrated mode: Applicative or Custom authentication modules

**URL:** <https://discuss.workflowgen.com/t/setup-iis-7-0-and-above-in-integrated-mode-applicative-or-custom-authentication-modules/616>\
**Category:** Authentication\
**Created:** [November 23, 2013, 6:28am UTC](https://discuss.workflowgen.com/t/setup-iis-7-0-and-above-in-integrated-mode-applicative-or-custom-authentication-modules/616 "2013-11-23T06:28:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wfg-admin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/wfg-admin/32/714_2.png) [@wfg-admin](https://discuss.workflowgen.com/u/wfg-admin)\
**Post date:** [November 23, 2013, 6:28am UTC](https://discuss.workflowgen.com/t/setup-iis-7-0-and-above-in-integrated-mode-applicative-or-custom-authentication-modules/616/1 "2013-11-23T06:28:15Z")

</div>

The process for registering a module in Integrated mode in IIS 7.0 or above is slightly different than the process for IIS 7.0 Classic mode.

The modules are registered in a new `system.WebServer` section in the `web.config`, instead of `httpModules` as in Classic mode or IIS 6.

When WorkflowGen Authentication is configured in Applicative or Custom mode, you have to manually edit the `web.config` to register the module.

Here’s an example for WorkflowGen Applicative authentication:

```auto
<configuration>
    <system.webServer>
        <modules>
            <add name="ApplicationSecurityAuthenticationModule" type="Advantys.Security.Http.AuthenticationModule"/>
        </modules>
    </system.webServer>
</configuration>

```