HTML5 Support for Integrated Authentication

HTML5 supports Integrated Authentication with ICONICS security, where possible.

Note: Not all browsers support this functionality, and the system must be configured to meet these specifications:

Both the server and the clients must be joined to the same domain (or trusted domains).
The IIS Application Pool of AnyGlass (IcoAnyGlass) must run under the LocalSystem account. (This is the default when installing.)
The Authentication settings of the AnyGlass application in IIS must allow “Windows Authentication” and must disallow “Anonymous Authentication”.
In the FrameWorX Server Location dialog, on the Servers tab, the Client Authentication must be set to “Integrated Windows Authentication”.
In Workbench, Security must be connected to Active Directory, and the Automatic log in option must be Enabled (this is the default).

Known Supported Browsers

Internet Explorer – Works out of the box.
Edge – Works from a remote machine, but not from the same machine as the IIS server. This is a known Edge issue.
Firefox – Additional configuration is necessary (it is required to add the server url into network.negotiate-auth.trusted-uris).

Chromium browsers (Chrome, Opera, etc.) – There is a known issue in Chromium which causes the NT-based login to fail for WebSockets. As WebSockets are necessary for HTML5 deployment, this means that these browsers cannot support Integrated Authentication until the issue is fixed. As of the publishing of this document, the issue has not yet been fixed, but it seems likely that it will be in the near future.