Contents x
    Release 4.13.2 Client
    • 18 Apr 2023
    • 3 Minutes to read
    • Contributors
    • Dark
      Light
    • PDF
    Contents

    Release 4.13.2 Client

    • Updated on 18 Apr 2023
    • 3 Minutes to read
    • Contributors
    • Dark
      Light
    • PDF
    Article summary

    Release 4.13.2

    Prerequisites

    Before installing ExactAccess 4.13.2, please ensure that the following requirements are met:

    On Client systems:

    .Net Framework 4.7 or higher

    .Net Core Framework Windows Desktop Runtime 3.1.x or higher

    .Net Core Framework ASP.Net 3.1.x or higher

    On Server systems:

    None

    Supported Operating Systems

    XA Client supports Windows 10 and Windows 11 (Windows 11 support was added in this release)

    XA Server supports Windows Server 2016 and Windows Server 2019

    Notable Improvements

    Added support in extension to save credentials for submitting form upon pressing Enter (HEALTH-158, HEALTH-276)

    Added feature to block specific URLs for a domain by adding partial URL matching. To configure this feature, see "FAQ Question 1". (HEALTH-268)

    Fixes

    Added support for SnapApp to work while switching between test server to the production server (HEALTH-87)

    Resolved issue of detecting any fields within all websites in the same domain when the URL is changing (HEALTH-90)

    Updated extension manifest files location to XA software installation directory. Also moved related registry settings from HKCU to HKLM. (HEALTH-4)

    Corrected saving and fetching Auto-Submit setting to handle auto-submit feature for sites for Chromium & Firefox browsers (HEALTH-28)

    Fixed in Chrome & Firefox NTLM files to handle SnapApp extension's behavior with NTLM sites (HEALTH-159)

    Fixed issue related to disconnecting current user's session while tapping card user on Citrix receiver end (HEALTH-362)

    Note:

    If the first user takes 1.5-2 minutes' time on the Hyperspace window after logging in to Hyperspace, and after that, a second user taps over the session, then only the current user will show in Task Manager and there will be no issues.

    Badge scanning was disabled on Windows log out or tap over (HEALTH-363)

    Backward Compatibility

    Upgrade from 4.11.6 to 4.13.1 or to 4.13.2 is supported

    Upgrade from 4.12.5 to 4.13, or to 4.13.1, or to 4.13.2 is supported

    Upgrade from 4.13.0 to 4.13.1 or to 4.13.2 is supported

    Upgrade from 4.13.1 to 4.13.2

    FAQs

    Question: How do I disable SnapApp extension to ignore a specific webpage (e.g. password reset, forgot password, etc.)?

    Solution: We have to add a DisablePageSSO registry setting to disable SnapApp extension to ignore a specific webpage (e.g. password reset, forgot password, etc.).

    Follow these steps to cause SnapApp to ignore a specific webpage:

    DisablePageSSO_Folder.jpg
    Example
    In this example, we have a domain cloud.tenable.com on which we want to disable the SnapApp extension for some pages/URLs.

    We have two URLs: a Login Page URL and a Forgot/Reset Password Page URL.

    Login URL Page

    Forgot/Reset Password Page

    Note

    There is a dynamic part after the word "password-reset" on this URL. This could be anything like a user ID, category info, or a GUID. We have to exclude that part of the URL when adding it to the DisablePageSSO setting in the registry.

    Case 1: When a user enters the login page URL, it will not match the existing URL in the registry. So SnapApp will work as usual.

    Case 2: When a user enters the password reset page URL, it will match with the existing URL in the registry with the help of the Wild Card Pattern Matching process. We check the registry URL with an asterisk (*-the wildcard used in matching) included at the end of the URL that the user has entered. In this case, the user's URL will match with the existing one, and SnapApp will disable for that page and will not fetch & set credentials there.

    Note:

    DisablePageSSO setting is an advanced setting for SnapApp and will not be in the registry by default. If we want this feature, we have to add this setting under SnapAPP Settings in the registry.

    On a client system with XA Client installed, open the registry editor and navigate to this path:

    Computer\HKEYLOCALMACHINE\SOFTWARE\HealthCast\eXactACCESS\SnapAPP Settings

    Create a new key under SnapApp Settings and set its name to DisablePageSSO.

    Next, under DisablePageSSO, create a new key with the name of the domain of the relevant site.

    Note:

    Ensure you only use the domain name without any www, HTTP, or https.

    Next, for the domain name key, add the specific URLs as string values in the right panel as shown below.

    Note:

    URLs added here should NOT contain the dynamic part, like any query string value or any parameter for username or ID.

    SnapApp will check for the DisablePageSSO setting in the registry and then will check for the domains. If the domain of the current URL exists in this list, then SnapApp will check for the blocked URLs for that specific domain and will exclude those URLs from its default behavior, meaning it will not fetch and set credentials for that URL.

    This process uses WildCard Pattern Matching to match the current URL with the partial URLs specified here.

    Was this article helpful?
    What's Next