ApplicationXtender - License Service - License Error

Applies to - ApplicationXtender Web Access.NET 8.0, 8.1, 16.3, 16.6 when using Chrome browser

Summary

Cause

ApplicationXtender 8 and higher when using .Net Framework 4.7 or higher causes an error when certain Microsoft security patches are applied.

OpenText has provided information regarding the updates and attributes the error to security changes involving the way browsers handle cookies as documented in provide kb article below.

https://support.microsoft.com/en-us/help/4533013/kb4533013-cumulative-update-for-net-framework

Resolution

The steps below will work with Chrome until version 91.

If the environment is running on .net framework 4.7.2, update the web.config file of WebAccess site as below typically located at c:\inetpub\wwwroot\ApplicationXtender on the web server.

Make a backup of the current web.config file first and then add an attribute "cookieSameSite" with value "None" to the node "system.web/sessionState"

<sessionState cookieName=”ASP.NET_SessionId_Wx” cookieSameSite=”None” />

NOTE – If you copy/paste the above link make sure to ensure the double quotes are true quotes.

Open

Once saved the website will refresh and should resolve the license issue going forward.

It is also recommended to restart the license service in order to ensure the licenses consumed are cleared out.

Secondary the fix above does help in alleviating most cases.
In the event the license still climbs beyond available licenses please also apply the following steps for each user that is using Chrome.

Open Chrome on the workstation
Go to chrome://flags

Search for #same and disable the flag below
#same-site-by-default-cookies

Search for #cookies and disable the flag below
#cookies-without-same-site-must-be-secure

For Chrome version 91 the below method will work until Chrome version 94 is released in September 2021.

Modify shortcut or launch Chrome using the flags provided below.

• for Mac

  • /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure 

• For Windows

  • Chrome Application Path --disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure

    • Example - "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure 

Edge uses the same flags and can be called similarly

• For Windows

  • Edge Application Path --profile-directory=Default --disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure

    • Example - "C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --profile-directory=Default --disable-features=SameSiteByDefaultCookies,CookiesWithoutSameSiteMustBeSecure

Once Chrome version 94 is released the command line interface options above will no longer work.

OpenText recommends upgrading AX to a minimum of Version 16.6 and implementing SSL (HTTPS) on AX sites to prevent the issue in Chrome and Edge going forward.

Additional documentation regarding recommendations for upgrading AX to the latest version and implementing SSL (HTTPS)

Open