Hello Phil! Thank you for reaching out.
First of all, please know that we understand your frustration. Let me assure you that this issue is equally annoying for us and that we want this to change just as much as you do.
The technical reason why the GTN750 can store your credentials while our panel is unable to do so is very simple, let me try to explain.
The user interface of the GTN750 is displayed by rendering files that are stored locally on your computer, more specifically in the PMS50 GTN750 addon. It stores its credentials in a custom storage that Asobo has created, which (after some initial bug fixes) is able to persist tokens between sessions.
In contrast, our panel uses an iframe that can be conceptually compared to having a “portal” to an online website. The difference between “local” addons such as the GTN750, and iframed panels such as ours, is that the latter has no direct communication path with the simulator. This is because of globally established security protocols, not a Navigraph or Asobo decision. This means that we are not able to access this “custom store” that the GTN750 makes use of.
“Well how is this fixable by Asobo?”, you might ask. Good question! Asobo, as developers of the simulator, are responsible for implementing the technology/environment in which the panels are run, called Coherent. This environment is basically a web browser, closest resembling Safari.
When web browsers such as Safari encounter iframes on the web, they set up separate storage locations dedicated to the environment within said iframes automatically. That storage is then persisted between browser restarts. This is not the case in Asobo’s implementation, forcing developers to use their local-only solution in order to achieve persistence.
We have wired everything up for a working, secure solution. All we need for persistence to work is for Asobo to adapt to the specification of localStorage, which they can seriously do with the flip of a switch. We have confirmed this with the developers behind the Coherent environment directly. Until they do, we cannot persist your credentials. At least not securely or according to standards.
With all of the above said, and having mentioned that we want this solved as much as you do, we have been experimenting with both non-standard and insecure solutions. We can easily provide insecure solutions, but as you can imagine, we do not want to do that for obvious reasons.
We have a few experimental non-standard solutions that might work without security implications, but due to the ongoing development of the next Charts product, we are limited in the time that we can spend on verifying their integrity. Therefore, we hope that Asobo will honor their promise of flipping the switch, even if it has been almost a year since they said they’d do it.
There you go, I hope this was informative enough! Let me know if you have any questions and I’ll do my best to answer them.
Kind Regards,
Malte