Known Issues - Browser Related Issues

Known Issues - Browser Related Issues

Authentication Failed Error when logging into Prolaborate

Description 

The customer was unable to log in. Error message: Authentication Failed 

 
 

Possible Reason 

The bookmark might have captured the existing state ID. 

Workaround 

State IDs are captured at the login page for enhanced security from Prolaborate V4.4. When the login page is bookmarked, there is a possibility that the bookmark captures the existing state ID, which results in an authentication error. 
This can be fixed by clearing the cache in the browser.
  1. Clear the bookmarked URL in your browser. Go to your Favorites/Bookmarks and delete any instances of the Prolaborate URLs.
  2. Press F12 on the Prolaborate login page, this will open the Developer options.
  3. Now right-click on the reload page and click Empty Cache and Hard Reload.
  4. After that, try accessing the Prolaborate environment using the URL itself. 

  

Email Response

(Initial Troubleshooting to Clear Bookmarked URLs, Browser Cache and access using the Prolaborate URL)
Hi <Customer>,

Thank you for reaching out to Sparx Platform Support. 

We have investigated your environment, and it appears to be functioning without any issues. However, we suspect that the Authentication Failed error might related to the bookmarked URL. We kindly request the user to try the troubleshooting below and provide us with the outcome. 
  1. Clear the bookmarked URL in your browser. Go to your Favorites/Bookmarks and delete any instances of the Prolaborate URLs.
  2. Press F12 on the Prolaborate login page, this will open the Developer options.
  3. Now right-click on the reload page and click Empty Cache and Hard Reload.
  4. Please use the URL provided below to access Prolaborate environment. 
  5. <Prolaborate URL> (Please try accessing the URL in a private tab for the first time)
If the issue persists, we kindly request the user to record a short video of the issue. This will help us to understand the behavior and assist you promptly. 

Please feel free to reach out if you have any questions or need assistance regarding this.

Reference

Ticket ID: #8287
Subject: VMo2 ST32 'Authentication Failed' error when accessing the platform
Department: Sparx Platform Support


Authentication Failed Error for Active Directory Users on First Login Attempt

Description 

Active Directory users are encountering an "Authentication Failed" error when attempting to log in to Prolaborate for the first time.
 

Possible Reason 

The issue may arise if users have bookmarked the entire URL instead of only bookmarking the domain name and port number.

Workaround 1

State IDs are captured at the login page for enhanced security from Prolaborate V4.4. When the login page is bookmarked, there is a possibility that the bookmark captures the existing state ID, which results in an authentication error. 
This can be fixed by clearing the cache in the browser.
  1. Clear the bookmarked URL in your browser. Go to your Favorites/Bookmarks and delete any instances of the Prolaborate URLs.
  2. Press F12 on the Prolaborate login page, this will open the Developer options.
  3. Now right-click on the reload page and click Empty Cache and Hard Reload.
  4. After that, try accessing the Prolaborate environment using the URL itself. 

  


Workaround 2

Another solution is for the customer to bookmark only the domain name and port number, which should resolve the authentication issue.

Reference

Ticket ID: #10180
Subject: Fwd: Registered Support Request - Authentication Issue in Prolaborate
Department: Prolaborate Support

Vulnerabilities (Unsecured Session Cookie Transmitted Over HTTPS)

Description

We have identified a session cookie that is not marked as secure and is transmitted over HTTPS. The vulnerability lies in the ASP.NET_SessionId Cookie source HTTP Header.  Moment.js is outdated and it suffers from an improper limitation of a pathname to a restricted directory ('Path Traversal').

Possible Reason

We have verified the reported issue with our Product Team and found that the reported issues be addressed in the Prolaborate v3.7. 

Workaround

The team has promised a patch for Prolaborate V3.7 for the vulnerabilities reported. We have also seen that our customer had upgraded from V3.5 to 3.6 and now to v3.7 because of the vulnerabilities identified.  Our recommendation from the product team is to set up Prolaborate V4 in the test/production environment.

This is because of the following reasons.
  1. VAPT is done against Prolaborate V4.
  2. The application is fully compliant with security standards the newly reported issues are handled in the latest version. 

Reference

Please refer to the below link for Installer and upgrade instructions. 

https://prolaborate.sparxsystems.com/resources/release-history/release-notes-v3?id=370

Tags

login error,
authentication failed,
browser cache issues,
unsecure session cookie.


    • Related Articles

    • Troubleshooting: Authentication Failed when Logging in from Remote Desktop

      Issue Title: Getting “Authentication Failed” error when logging in from a remote desktop Description The customer was creating a new environment with Prolaborate 4.2.1. They were able to access the environment on the server machine without any ...

    • Troubleshooting - Browser related issue

      Q1: Getting “Authentication Failed” error when logging in from a remote desktop Description The customer was creating a new environment with Prolaborate 4.2.1. They were able to access the environment on the server machine without any problems but ...

    • Known Issues - Charts

      Q1: Roadmap Displaying EA GUID Values When Grouping by RefGUID Property Description The customer reports that when grouping the roadmap items by a property of type 'RefGUID', the roadmap shows the EA GUID values of the referenced elements. We were ...

    • Known Issues - EA Connection error.

      Error in Could not connect to the Sparx Systems Floating License Description: The Customer encounters an error as follows when accessing the servers from our client computers. Workaround: To conduct a browser test to ensure everything is functioning ...

    • Known Issues - Migration

      Q1: "Invalid License" or "License Missing" error after migrating Prolaborate to a new server Description The Prolaborate and Pro Cloud Server is migrated to a new Server setup. After logging into Prolaborate, an error message appears saying "Invalid ...