Advanced Authentication 6.3 Service Pack 3 includes new features, enhancements, improves usability, and resolves several previous issues.
Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the Advanced Authentication forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources. You can also post or vote the ideas of enhancement requests in the Ideas forum.
For more information about this release and for the latest release notes, see the Documentation Advanced Authentication NetIQ Documentation page. To download this product, see the Advanced Authentication Product website.
If you have suggestions for documentation improvements, click Advanced Authentication NetIQ Documentation page.at the bottom of the specific page in the HTML version of the documentation posted at the
Advanced Authentication 6.3 Service Pack 3 provides the following new features, enhancements, and fixes in this release:
This section provides details of features by category:
This release introduces the following feature:
In this release, Advanced Authentication introduces a new feature to configure multi-factor authentication for RADIUS clients in Microsoft operating system. The NPS Plug-in can be installed and configured to work with Microsoft NPS and brings the multifactor authentication for RADIUS Client configured on the Network Policy Server.
For more information, see Advanced Authentication - NPS Plug-in Guide.
This release introduces the following features:
In this release, Advanced Authentication introduces a new feature called Support Assisted Logon. The Support Assisted Logon feature is for users who do not use the multi-factor authentication and forgot the password. Using Support Assisted Logon, the Helpdesk Administrator can access the Windows workstation with the Helpdesk Administrator’s credentials.
Later, the feature will be improved to bring the Support Assisted Logon for the users who use the multifactor authentication and can't login because they forgot their card or lost authenticators.
This release includes the following enhancements:
This release includes the following Server enhancements:
In this release, Advanced Authentication includes Risk Service 2.0. NetIQ Risk Service protects against high-risk authentication and application access requests. It evaluates the level of risk during each access attempt by using contextual information without influencing the end-user experience. This prevents fraudulent access to secured web resources.
For more details, see Risk Service 2.0.
In this release, Advanced Authentication allows the administrator to upload the intermediate certificate in .p7b format for PKI method enrollment.
In this release, Advanced Authentication improves the speed of full synchronization with eDirectory repository.
In this release, Advanced Authentication enhances the capabilities of Web Authentication. Following are the major capability changes for Web Authentication:
OAuth 2.0 event supports integration with OpenID connect.
Ability to reset Client secret for OAuth 2 events. The new capability enables the administrator to reset the client secret when needed. For more information, OAuth Event in the Advanced Authentication - Administration guide.
Added text customization capability for OAuth 2.0 and SAML 2.0 events. For more information, see Customizing the Login Page of Web Authentication Events in the Advanced Authentication - Administration guide.
In this release, thefield in the PKI authenticator enrollment portal populates only the certificates with the authentication key and its expiry date.
It is possible to click the buttonto show all the certificates.
In this release, Advanced Authentication allows the Help Desk Administrator to set the Emergency password expiration time in minutes. The time is specified based on the local time of the browser.
In this release, Advanced Authentication introduces a new option calledto limit the amount of SMS OTP, Email OTP, Smartphone, and Voice OTP authentications. The new option prevents the user from authenticating using a chain where SMS, Email, Smartphone, and Voice OTP authenticator is the first authentication method.
This release includes the following New Enrollment Portal enhancements:
In this release, the New Enrollment portal supports Flex OTP.
In this release, Advanced Authentication stops displaying version number and the product name in the New Enrollment portal.
In this release, Advanced Authentication supports multiple enrollments of the same authenticator in the New Enrollment portal.
In this release, Advanced Authentication displays the legal notice in the browser language.
This release includes the following security enhancements:
In this release, Advanced Authentication upgrades the third-party components to address vulnerabilities reported against them. Since those vulnerabilities were non-impacting on the product, the upgrade is being done for forward continuity.
In this release, Advanced Authentication stops supporting weak ciphers diffie-hellman-group14-sha1.
This release includes the following Smartphone enhancements:
In this release, Advanced Authentication supports multi-factor authentication when the user enrolls the Smartphone authenticator using the enrollment link if a multi-factor chain is added to the Smartphone Enrollment event.
In this release, Advanced Authentication removes the tenant name from the NetIQ mobile application’s authentication request description when the user logs in using the Smartphone method.
This release includes the following client enhancements:
Previously, face biometric could be spoofed with a printed picture or picture on a mobile device. In this release, Advanced Authentication uses blink detection to differentiate live face and photos. You can configure Device Service to enable blink detection. After configuring, the user needs to blink to get authenticated. You can configure the number of blinks in service settings.
In this release, Advanced Authentication allows the users to customize the background image of the login page in Windows 10. Perform the following steps to customize the background image:
Open> > .
In thesection, select .
Clickand select the image to set.
NOTE:Advanced Authentication does not supportor to set as background.
In this release, Advanced Authentication automatically hides the methods which cannot be used at the specific moment. Following are the situations when Advanced Authentication hides the chains.
Bluetooth containing chains will not be shown when Bluetooth is not available or the Device Service is not installed.
Card, PKI, u2f containing chains will not be shown when the Device Service is not installed.
Touch ID containing chains will not be shown when Touch ID is locked / not enrolled / unavailable or the Device Service is not installed.
Windows hello containing chains will not be shown when devices are not available or the Device Service is not installed.
Face containing chains will not be shown when the Device Service is not installed.
In this release, Advanced Authentication fixes the issues with the Facial Recognition method in Mac OS. Mac OS users can use Facial Recognition for unlocking the operating system, FUS (fast user switching), authentication for operating system setting change, etc.
The Facial recognition cannot be used for login after boot.
Advanced Authentication allows administrators to localize error messages, method messages, and prompt messages displayed on endpoints to an unsupported language.
This release includes the following software fixes:
This release includes the following Server fixes:
When the administrator tries to add some LDAP Servers in the repository configuration, Advanced Authentication does not check whether the added LDAP servers are valid and reachable or not.
Since Advanced Authentication 6.3 Service Pack 1, it was possible to add the same RADIUS Clients many times. Due to that issue, the RADIUS configuration file lost RADIUS secrets. It caused the authentication issues after upgrading to Advanced Authentication 6.3. Service Pack 2. Those duplicate RADIUS Clients need to be removed manually. After this release, it is not possible to add the duplicate RADIUS Client entries.
When the user uses some special characters in the password, the RADIUS logs display the passwords in clear text in Debug mode. After this release, passwords that contain all the possible characters are masked.
When the user tries to authenticate using the Smartphone method, the login screen keeps refreshing, and the user cannot enter the OTP to authenticate.
After updating to Advanced Authentication 6.3 Service Pack 2, the administrator is not able to see the web portals of Advanced Authentication whenis enabled.
When the administrator uses an activation key to get access to the Advanced Authentication update channel, it fails and the following error message is displayed.
Query installed language failed. (134) No matching items found.
When the user tries to enroll theauthenticator with the current password, it gets enrolled. After this release, the enrollment checks the password for uniqueness.
When the administrator enablesin the Web Authentication policy, the message is displayed without phone numbers or Email address. It's not possible to customize the messages to have the phone numbers and email addresses shown in the Web Authentication dialogs.
Advanced Authentication no longer has the Recipient mask policy. Advanced Authentication 6.3 Service Pack 3 and newer versions always mask the phone numbers or Email address and the text containing the masked value is shown on the Clients, portals and Web Authentication.
When users perform authenticating Web Authentication with the TOTP method,option is displayed.
When an administrator tries to boot up or restart the Advanced Authentication server, there is a delay and a Appliance is under maintenance / starting up message is displayed in the browsers. Also, the client devices display server error messages to the users during OS logins.
In Custom messages policy, the inputs for each locale's custom messages are displayed right-to-left despite the locale that is selected for.
English is not set as the default language on the browser. However, the labels on the login page are displayed in English. The labels are updated to the default language only when the user starts typing the user information.
Advanced Authentication 6.3 Service Pack 3 includes the following client fixes:
If a user is a member of a repository of a hundred thousands of users and the Please wait message is displayed. After some time, a Server not found message is displayed even if the server is reachable.option is enabled for the repository and tries to authenticate, a
Solution : The fix is only for Active Directory repositories. If a user experiences the issue with the eDirectory repository, disableoption in repository’s .
When the settings are configured to automatically select the last used chain and the linked chains are used, every time the user has to select the linked chain manually once the grace period expires. However, for the required chain, it works as expected.
When a user tries to enroll or test the Bluetooth authenticator, Bluetooth device driver fails to detect the Bluetooth devices present around and a not found SHA 256 error code 0 message is displayed in the logs.
This release includes the following Mac OS Client fixes:
In domain mode, some of the used methods are not cached in Mac OS X Client. Hence, in offline mode, all the chains are not displayed. After this release, the used methods cached properly.
When the user tries to log in, instead of the actual list of enrolled chains, the login window displays the chains which were available for the previous user.
When a user tries to unlock OS in offline mode, sometimes a Chains not found message is displayed when the user is already logged on before.
When the user tries to unlock an existing session, the input field is not correctly placed until the user clicks the input field.
Advanced Authentication 6.3 Service Pack 3 includes the following Windows Client fixes:
After Windows 10 2004 update, the Windows Client does not correctly apply the Multi-Factor Authentication logon tag group.
When the user is in a Remote Desktop session, and inserts a U2F token or taps a card, the system locks automatically.
When a user's laptop run out of battery or the user switched it off, the config.properties file gets corrupted.
When the user tries to cancel a Remote Desktop Protocol (RDP) login, Windows Client window is closed but the RDP screen appears to stay open with a new login screen and it allows the user to enter their username.
When the user needs to select the chains while accessing the Windows tablet, the arrow down button does not work. This issue happens only on the devices with a touch screen.
When the user sets the Windows Hello Pin using alphanumeric characters and tries to authenticate, the authentication fails and a The PIN is incorrect message is displayed.
When the user tries to unlock a Windows workstation, it requests the user to specify the Windows Hello PIN twice to authenticate.
A second user is not able to login to Windows as the Windows Hello PIN is prompted for the last logged on user.
Windows Hello PIN is prompted to all the users irrespective of whether the users have enrolled the authenticators or not.
Advanced Authentication 6.3 Service Pack 3 includes the following VDA fix:
In kiosk mode settings, when the configured user group is assigned to another user group as its member, the functionality does not work as expected and the user is not able to quit from the VDA shell.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
Advanced Authentication 6.3 Service Pack 2 includes the following known issue:
A full synchronization of the Active Directory repository may be failed to unknown reason. In the logs, administrators may see the following error:
socket sending error [Errno 104] Connection reset by peer.
Probably, this is a defect in the updated third-party module.
When administrator updated email address or phone number for a user in eDirectory, there is a 5 minutes delay in updating the information in the user's authenticator.
You can update Advanced Authentication 6.3.0, 6.3.1, 6.3.2 to 6.3.3.
The Repo Agent will be discontinued in Advanced Authentication 6.4. It is replaced in Advanced Authentication as a Service (SaaS) by the Cloud Bridge integration.
For more information about upgrading from 6.2, see Advanced Authentication- Server Installation and Upgrade guide.
NOTE:The recommended upgrade sequence is the upgrade of Advanced Authentication servers, followed by plug-ins and Client components. Any change in the upgrade sequence is not supported.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information website.
For general corporate and product information, see the NetIQ Corporate website.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent policy, and FIPS compliance, see http://www.microfocus.com/about/legal/.
© Copyright 2020 NetIQ Corporation, a Micro Focus company. All Rights Reserved.