Workflow 8.8.1 - when installed on new server, the autologin to ProcessManager page might not work
search cancel

Workflow 8.8.1 - when installed on new server, the autologin to ProcessManager page might not work

book

Article ID: 442365

calendar_today

Updated On:

Products

IT Management Suite

Issue/Introduction

Installing Workflow Server on new OS instance, you might notice that everytime when opening a ProcessManager page, you would be challenged with entering username and password

Environment

Workflow 8.8.1

Installed on 2022 or 2025 Windows Server

Cause

WF 8.8.1 was expecting to have IIS 6 compatibility during installation for some parts of installation phase

Absence of IIS 6 compatibility causes our internal installation scripts to misconfigure certain ASPX pages participating in autologon process.

Resolution

Issue will be resolved with next WF release, starting from 8.8.2 version.

If all other pre-requisites are met:

1) User is logged on to machine where he launches the browser as AD user

2) Internet options have at least the following two options configured:

Automatic logon switched ON  for intranet sites

The base URL of the Process Manager machine is added to the list of trusted sites

3) Process Manager Ensemble Settings allow AD authentication:

4) AD user must be an existing user (registered as AD user) in the ProcessManager Database - till 8.8.1 including

The AD Sync Profile (associated with the user performing the login) setting "Auto Create User on initial Logon"  is enabled.

Workaround the issue:

Open IIS select Process Manager and select Content View, then find WindowsAuthentication.aspx file and double-click on it and then in right pane click link "Switch to Features View":

After switching to "Features view"  open "Authentication" settings for file WindowsAuthentication.aspx
Make sure the settings have Forms and Windows Auth enabled, but rest of auth are disabled (anonymous, asp.net and basic).

Restart of IIS might be required. And after those steps - the auto-login (login bypass) should work for Registered AD Users.