Configuring Security

Security settings are configured in the Softadmin® interface and are specific to each server instance and deployment. The same MCP server can run with different security configurations depending on the environment. For example, a development instance can use No security, while a production instance of the same server can use OpenID Connect.

Security settings are not deployed. After deployment, a new MCP server cannot start until its security settings have been configured.

Configuring the IIS

Conceptual

Create a separate IIS application for each MCP Server in the system.

Each application uses a unique alias, but all applications point to the same physical directory: Mcp\bin.

URL	Physical path
https://myserver/mysystem/mcp-customers	D:\Web\MySystem\Mcp\bin
https://myserver/mysystem/mcp-employees	D:\Web\MySystem\Mcp\bin

The application pool needs
.NET CLR Version: No Managed Code
Managed pipeline mode: Integrated

Step by Step

Follow these steps to expose an MCP Server defined in the Softadmin® system.

1. Open IIS Manager.
2. Locate the Softadmin® system in the site tree.
3. Right-click the system node (not the Mcp directory), then select Add Application.
4. Set Alias to match the IIS Application value configured for the MCP Server.
5. Set Physical Path to the <path>\Mcp\bin directory.
6. Assign an appropriate application pool.