Publish the Web Applications
On this page
Installing a Web App, Self Service Portal, or API package and publishing an instance of it are two separate acts. The package installs a template; it does not create a running site. The Web Configuration tool turns an installed template into a published instance: an IIS site of its own, or a virtual directory under a site. You can publish more than one instance from the same installed package.
The Web Configuration tool
The tool is installed under
Common Files\Alloy Shared\Alloy Navigator\<version>\bin, and you can start
it directly from that folder. The Alloy Control Panel lists it when it is
present on the machine. The Alloy Control Panel also lists the web instances
published on the machine, except an instance whose registry values are
incomplete. The Web App package adds a Web Configuration shortcut to
the Alloy Software > Alloy Navigator folder of the Start menu. The
shortcut is not in the Alloy Software > Alloy Navigator 2026 >
Tools folder; that folder holds Automation Server, Database
Management, Settings, and Import.
The publishing wizard
The same seven-page wizard configures the Web App, the Self Service Portal, and the API. Which pages you see, and where the wizard starts, depends on the command you start it with:
- Creating an instance runs all seven pages in order.
- Configure > Full and Configure > Database start on the Database page.
- Configure > Web starts on the Installation Type page and skips the Database page.
- The Virtual Directory page is left out when the instance is published as a web site of its own.
- The URL page appears only when you are creating a new instance.
The pages are:
- Database - specify how the web application connects to the database. The Key list holds the registered Database Access Keys. Choosing a key fills in SQL Server and Database from it; you can then type a different server or database over them, and typing a different server clears the database field. Import Key... opens the import dialog and then selects the imported key. Next is available only when all three fields are filled, and it opens the connection. The wizard remembers the key you last used, per Windows user, and selects it next time.
- Installation Type - choose Install as a Web site or Install into a virtual directory. Choosing either clears the instance's URL and cancels any pending change to the link macro.
- Web Site - select Choose an existing site, or select Create a new site with the following parameters and fill in Site Name, IP Address, Host name, Port, and Physical Path.
- Virtual Directory - type a name for the new virtual directory, or,
when you chose an existing site, choose one of the directories already
published under it. Typing a name recomputes Physical Path: by
default, a folder under the
WebAppsfolder named after the application (Web,SSP, orAPI), then the site, then the virtual directory, with a number appended when that folder already exists. You can change the path, except for the package's own default instance, where it is read-only. Next refuses a name that contains any of\ ? ; : @ & = + $ , | " < > *, and refuses a physical path whose root does not exist, a path another instance already uses, or a path nested inside another instance's. It asks for confirmation when another instance already uses the virtual directory. - Authentication Method - see Authentication Method page.
- URL - review the URL computed for the new instance, or enter the
correct URL yourself. Next is available only when the URL starts
with
https://and is longer than eight characters. The page compares the URL with the system macro that workflow notifications use to link to this instance: Web Portal Link for the Web App, Self Service Portal Link for the Self Service Portal, or API Link for the API. While the macro has a value that differs from the URL and you have not chosen an update yet, the page shows Mismatch detected with two buttons: Update system macro with instance URL rewrites the macro when you apply the settings, and Update instance URL with system macro copies the macro's value into the URL box. - Ready to Apply Settings - review the whole configuration and click Apply, or click Previous to change a setting. You can copy the summary with Ctrl+C, Ctrl+A, or its context menu. This is the only page that applies your settings; the earlier pages only collect them, except that a successful Next on the Database page already saves the key the wizard selects the next time. A Configure > Database run restarts the web application when it applies.
Because the URL page appears only when an instance is created, reconfiguring an existing instance does not correct its link macro: a Configure > Full or Configure > Web run fills the macro only when it is empty, and a Configure > Database run does not change it. The three link macros are edited in the Settings App, in its Links group.
Authentication Method page
The Authentication Method page asks you to choose the authentication method for the application's users (Web App), visitors (Self Service Portal), or calls (API). It offers Windows Authentication and Standard Authentication; for the API, the second is Access Token Authentication, and the page states that applications supply the Windows domain credentials of their account, or an application ID and secret, or a user name and password. A new instance starts on Standard, with password authentication allowed. LDAP and single sign-on are not choices on this page. An upgrade from a version earlier than 2024.2 that passes through this page carries no single sign-on providers of the older installation over. When the settings imported from an older installation had password authentication turned off, the page does not let you go on with Standard.
Windows authentication is kept in a different place for each application:
- For the Web App, it is an entry in the instance's
Web.config, not a database setting. The shipped configuration uses Standard and has IIS Windows authentication turned off. Choosing Windows Authentication on this page for a Web App instance, when you create it or run Configure > Full or Configure > Web, sets that entry to Windows, turns IIS Windows authentication on for the instance, and turns anonymous access off; no separate step in IIS is needed. Choosing Standard Authentication turns IIS Windows authentication off and anonymous access on. The Windows Authentication feature of IIS must be installed on the server. With Windows authentication on, the Web App signs the user in with their Windows identity and hides the sign-out control. - For the API, it is the IIS Windows authentication setting of the
application. With it on, the API offers no access token authentication:
it has no token endpoint, and a POST request to
/tokenreturns a response saying that access token authentication is not configured. - For the Self Service Portal, it is part of the portal's settings in the database. With Windows authentication on, the portal offers Windows sign-in and does not show the password form: it takes the customer's name from the Windows identity that IIS established, so the customer types nothing into the portal. Whether the browser passes the Windows credentials silently or asks for them depends on IIS and the browser. The portal's Windows sign-in answers only when Windows authentication is also enabled in IIS for the portal; see Install the Self Service Portal.
See Authentication Methods for how each method works for users.
Instance commands and information
The tool's window, titled Web Configuration, lists each IIS site that has
an http or https binding as a tree node named after the site, with each
published application under it as a child node named after its virtual
directory, and an icon that shows the instance type. Selecting an instance
shows its information page. The page has the same layout for a Web App, a
Self Service Portal, and an API instance:
- The heading names the instance type, Web App, Self Service Portal, or Alloy Navigator API, and holds the Restart and Configure... buttons.
- The Database category shows SQL Server, Name (the database name), and Access Key, with a Configure... button.
- The Web category shows Name (the instance's display name), URL, Site, Virtual directory, Physical path (the folder of the instance's IIS application), and Authentication, with a Configure... button. The Virtual directory line is left out for an instance published at the root of a site. The URL is computed from the site's binding, and an https binding is preferred.
- The Error Logs category reads "No errors were logged." or "There are some errors logged." and holds Clear and View Details, which are unavailable when nothing is logged. Clear first asks "Are you sure to delete error log?"
Authentication reads Windows when Windows authentication is turned on in IIS for the instance, and Standard otherwise; for an API instance, it reads Access Token instead of Standard. For a Web App or Self Service Portal instance on Standard whose password authentication is turned off, it reads Standard (SSO only).
Below the page, a line reads "Customize this instance in the Admin Center (Web App > Admin Center > Apps and Portals)." When the instance has an error, a bar below the page names it: "Physical path does not exist.", "Invalid Virtual Directory.", "Invalid Site.", or "Invalid Config file(s)."
A path shown in the information page, such as the Physical path value, is a link that opens the folder in File Explorer. The URL value is a link that opens the address in your default browser.
The menu bar has three menus:
- File holds Create, with one item per application: Web App, Self Service Portal, and Alloy Navigator API. It then holds IIS Management, with Start IIS Manager and Restart IIS, and Exit.
- View holds Refresh (F5).
- Help holds Help Contents and Debug Information. Debug
Information writes
WebConfigDebugInfo.txtto your temporary folder, with the machine's and IIS's details, each instance'sweb.configand configuration files, and log file content, and opens it. The tool builds its help links itself, todocs.alloysoftware.com; changing the help URL set for the product does not change them.
Delete, Restart, Configure (Full, Database, Web), and Configure Site are on the instance tree's context menu, not on the menu bar. Configure starts the publishing wizard described below.
Restart restarts the instance's application pool and reports that the instance has been restarted; the Restart button of the information page does the same. Both are offered for every instance of a type the tool recognizes, except an Admin Center instance.
Delete first asks "Are you sure that you want to delete the selected portal?" When you click Yes, it:
- removes the instance's IIS application, together with an Admin Center application nested under it and that application's pool;
- for an instance published at the root of a site, gives the site back its previous physical path and application pool when the tool knows them and they still exist, and otherwise deletes the whole IIS site;
- stops and deletes the instance's application pool;
- deletes the instance's physical folder, except for the package's own default instance;
- deletes the instance's data folder under
%ProgramData%\Alloy Software; - marks the instance's settings in the database as deleted, without erasing them; if this step fails, the failure is only written to the log.
The installed template is left as it is. Delete is not available for an Admin Center node or for an application whose type the tool does not recognize.
Configure Site is shown only for a site node, or for an instance
published at the root of a site, without a virtual directory. It opens the
Configure Site dialog with Site Name, IP Address (* or one of
the machine's addresses), Port, and Host name. When you click
OK, the tool renames the IIS site and rewrites the site's first binding
with the IP address, port, and host name. The dialog checks the name, the
IP address, and the port, and reports, for example, "A site with this name
already exists." or "This port is already in use." It does not change the
instance's files or its Web.config.
The web package installers also run the tool themselves:
- After installation, each web package's installer offers to run the tool to create an instance from the template you just installed. The offer is not made when the package is already installed, in an evaluation installation, in an administrative (network-image) installation, or when a major upgrade is detected.
- In an evaluation installation, the tool creates one instance without
showing its wizard, in a fixed virtual directory (
wpfor the Web App,hdfor the Self Service Portal, andapifor the API) and bound to a named Database Access Key. - On an upgrade, before the older version is removed, the installer saves the existing instance configuration to an XML file in a dated backup folder. After the new version is installed, it recreates the instances from that file, so you are not asked for the settings again.
- When a package is removed, its installer removes the instances that its template published.
Security headers
HTTP security headers for the Web App, the Self Service Portal, and the API
are added to the configuration of the IIS site that hosts them. The
applications as shipped send none of the headers below, and the Web
Configuration tool does not add them. The one exception is the Web App's
response to a download of a local file, which carries
X-Content-Type-Options: nosniff and
Strict-Transport-Security: max-age=31536000; includeSubDomains.
You can add the headers in IIS Manager or in the site's web.config file.
Start in IIS Manager, which creates the file, and then add the remaining
headers in the file.
| Header | Value |
|---|---|
Expect-CT |
enforce, max-age=43200 |
Content-Security-Policy |
default-src *; style-src 'self' http://* 'unsafe-inline'; script-src 'self' http://* 'unsafe-inline' 'unsafe-eval'; img-src 'self' http://* data:; |
Feature-Policy |
fullscreen 'none' |
Permissions-Policy |
fullscreen=() |
Referrer-Policy |
no-referrer |
Strict-Transport-Security |
max-age=31536000; includeSubDomains; preload |
X-Content-Type-Options |
nosniff |
X-Frame-Options |
SAMEORIGIN |
X-XSS-Protection |
1; mode=block |
For other values or other headers, contact Alloy Software Support.
In IIS Manager
- In IIS Manager, expand the server node and Sites, and select the site that hosts the Alloy web applications, typically Alloy Navigator Site.
- Open HTTP Response Headers.
- In the Actions pane, click Add.
- In Add Custom HTTP Header, type the header's Name and Value, and click OK.
In the web.config file
- Right-click the site that hosts the Alloy web applications, click
Explore, and open the site's
web.configfile. - Add or edit the
<customHeaders>section, above the closing</configuration>tag, with one entry for each header and its value. - Save the file and restart IIS.
For what an upgrade of the web applications replaces, see Upgrade a Production Installation.