![]() I cannot confirm this because i do not have the source code for the client and do not know what integrated browser they use. The error you are seeing is most likely a security issue raised by PSN because the integrated browser Galaxy Client uses is out of date. The plugin never gets those cookies because the login never succeeds. This tells the Galaxy to display a webpage (that URL in the previous comment), and, should you login successfully, take those cookies and pass them back to the plugin. The integration returns a "NextStep" object when this occurs. if that has also expired, you need to log in again. The application checks if you have a session cookie, and if it has expired, attempts to retrieve a new one via the refresh cookie. if you access GoG Galaxy fairly often, this likely won't be an issue. you will need to reauthenticate when that happens. However, there's a second cookie, called a "refresh cookie" that allows the caller to obtain a new "session cookie." After a period of two months of inactivity, the "refresh cookie" also expires. I believe this method is outlined in the GoG Galaxy Integration page for this issueĪ more technical note: Your login information is stored via a 64-bit cookie, known as a "session cookie". You also should only do so if you know what you're doing. It will expire very frequently and thus be pretty pointless. The only thing i can suggest for now is to try logging in again later, but hopefully this can get fixed in the client.Īlternatively, you can try logging in via the link and manually copying the 64 bit cookie into the plugin.py authenticate function, but i really do not recommend this. I'd like to test further, but upon trying earlier today, it suddenly worked again. If it is a browser issue, updating it would fix the issue. I have submitted a bug report to GoG outlining this. It may also be an issue of PSN being down, either in your region or for maintenance. ![]() This quiz does not pop up in the GOG Galaxy.Ī more technical note: Your login information is stored via a 64-bit cookie, known as a "session cookie". If that url results in a 404 page or something of the like, that is an issue with that link.įor me, i can successfully log in via that url, using Edge version 103 (the current version as of this writing) It may be worth noting that i have to do a verification quiz. if you get that same error in your browser, it is an issue on Sony's end. if you can do so, this is not an issue with this integration, but rather an issue with the Galaxy Client. If you paste this into your browser of choice, you can try logging in directly. format( redirect_url = OAUTH_LOGIN_REDIRECT_URL) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |