These release notes provide information about the One Identity Starling Two-Factor HTTP Module release.
One Identity Starling Two-Factor HTTP Module protects on-premise websites with Starling Two-Factor Authentication. Starling Two-Factor HTTP Module acts as a filter and requires users to authenticate through Starling Two-Factor Authentication to get access to the websites hosted on the web server.
New features in the Starling Two-Factor HTTP Module 2.3
The following is a list of issues addressed in this release.
|Resolved Issue||Issue ID|
|Non-admin User could not install Starling Two-Factor HTTP Module on a User Access Control system.||226014|
The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.
|Known Issue||Issue ID|
A warning message is displayed in Starling Two-Factor authentication page if the user has selected 'Use SSL' checkbox in the configuration tool and not configured LDAP over SSL in domain controller.
Configure LDAP over SSL in domain controller.
Starling Two-Factor authentication does not work if ISAPI agent and Starling 2FA HTTP module both are added for the same site.
Deselect the protected site from ISAPI agent.
Starling Two-Factor authentication may not be launched if user selects an inter nal path(s) or a section of a web application are selected.
Select the entire web application.