One issue that I came across with receiver 1.4 was that while they do create a unique session ID, it changes when the local storage for HTML5 is cleared out. This can happen if you are set to clear content when you close your browser or if you reboot or power off/on. Some applications tie settings to a specific user. While this may be ok for most applications, it causes major problems for other applications.
With that, I spent a few hours digging through inspects and code and found a solution that works for my company's needs. Just complete the following steps: (As always, make a copy of the file prior).
Image 1: This shows the local storage (left) and Session on the server (right). This is "prior" to the change:
STEPS:
Open the file "Default.htm.script.min". This is located in the following directory: "C:\inetpub\wwwroot\Citrix\StoreWeb\scripts"
Look for the line "if(c.username)".
Above that line add the following: "localStorage.setItem("ClientName", c.username);".
Save the file and reload your Portal.
Now you should be able to login and see the proper ClientName based off of your portal login as shown in Image 2:
I hope this helps anyone else that was facing the same issue I was.
Question
Steven Valinski
One issue that I came across with receiver 1.4 was that while they do create a unique session ID, it changes when the local storage for HTML5 is cleared out. This can happen if you are set to clear content when you close your browser or if you reboot or power off/on. Some applications tie settings to a specific user. While this may be ok for most applications, it causes major problems for other applications.
With that, I spent a few hours digging through inspects and code and found a solution that works for my company's needs. Just complete the following steps: (As always, make a copy of the file prior).
Image 1: This shows the local storage (left) and Session on the server (right). This is "prior" to the change:
STEPS:
Now you should be able to login and see the proper ClientName based off of your portal login as shown in Image 2:
I hope this helps anyone else that was facing the same issue I was.
Link to comment
4 answers to this question
Recommended Posts
Archived
This topic is now archived and is closed to further replies.