Hi Lee, I actually have the same/similar issue and started a thread about this recently: http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/1-0-0-LocalStorage-auth-instead-of-cookies-tp4996.html.
Probably best to merge my thread into yours. Nick/Mike, can you elaborate why this change was made? What was wrong with cookie-based authentication? Re: Nick's questions "What are you trying to accomplish?": I have software written that allows people to connect to multiple servers. 1.0.0 unfortunately breaks it.. Having different accounts is useful for segregation as well as for being able to automatically open the single session in the account. ________________________________ From: Lee <[email protected]> Sent: Monday, March 4, 2019 2:32 PM To: [email protected] Subject: Re: Authentication Changes in 1.0.0 Thanks Nick and Mike. The change ended up being on the front end & connection to the authentication module. We were destroying the users cookie if they tried to re-connect. With the changes to have that information in local storage, that broke our authentication process before it started. I suppose we'll have to see if deleting the local storage objects as well now will work. I just wanted to follow up in case someone found this thread and had a similar issue with an update from an older version to the new version that doesn't rely on cookies existence. -- Sent from: https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-guacamole-general-user-mailing-list.2363388.n4.nabble.com%2F&data=02%7C01%7C%7Cd7768f242b244885505508d6a0f15188%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636873355639043785&sdata=qSlYvrtCon6KYN%2FrmGT1kJarLIysNvTFpAX9nhtjokk%3D&reserved=0
