IIS
Prerequisites.
- A Windows Server that:
- Has the IIS feature installed.
- Has the latest Visual C++ Redistributable
- Has the SecurEnvoy Microsoft Server Agent.
- A Windows machine running the Single Agent.
1. SecurEnvoy RADIUS Profile.
- Go to Integration > Premises and add a new RADIUS profile.
- Enter the RADIUS configuration settings:
- Friendly Name.
- Server Port.
- Assigned Agent.
- The IP address of the Windows IIS server.
- The Shared Secret for the RADIUS connection.
- (Optional) Enable the 'Message Authenticator' and 'Brute Force Protection' options.
- Save the configuration.
2. MSA RADIUS Configuration.
- Go to the Microsoft Server Agent Config utility
- Enter the RADIUS configuration settings:
- The IP address of the Single Agent
- The Shared Secret for the RADIUS connection
- The RADIUS Port
- Click 'Update' to save the configuration.

Multiple Single Agents
Up to two Single Agents can be added in the Microsoft Server Agent. Each agent will require a RADIUS profile in Access Management.
3. MSA IIS Authentication.
- Go to the IIS Authentication tab in the Microsoft Server Agent Config utility.
- Click 'Include SecurEnvoy Plugin in IIS'.
- (Optional) Set a default domain name. Any username without a domain part will use this domain suffix.
- Click 'Update' to save the configuration.
- The MSA may prompt you to install the CGI and ISAPI Filter modules. Click 'Install' for these.

4. (Optional) IIS Configuration.
- Go to IIS Manager and open the SecurEnvoy plugin for the server.

- Configure the following optional settings:
- Authentication Timeout.
- Timeout on activity or after last auth.
- Override received hostname.
- Allow non secure connections.
- Default domain.
- Trusted networks (IP addresses).
- Logoff URLs.

5. IIS Site Configuration
- Go to the site in IIS and open the SecurEnvoy plugin.

- Configure the following options:
- Enable authentication on site.
- Protect all resources on site.
- Forms based authentication or HTTP Basic Authentication.

If 'Protect all resources on site' is unchecked you can enable it for each sub-resource on the site individually.