Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Login won't stay persistent after signing in. #6

Closed
1darklyte opened this issue May 11, 2021 · 14 comments
Closed

Login won't stay persistent after signing in. #6

1darklyte opened this issue May 11, 2021 · 14 comments

Comments

@1darklyte
Copy link

Using FF 88.0.1

After signing into HA using the add on it will not stay logged in. After a period of time (5+ min) it logs me out and asks me to log in again.

@bokub
Copy link
Owner

bokub commented May 11, 2021

After you're logged out, what happens if you visit Home Assistant directly? (not through the extension)

@1darklyte
Copy link
Author

1darklyte commented May 11, 2021

My HA session accessed at the same URL is always connected via a browser window and stays logged in even when the extension logs me out. Same experience with the HA Android App, it doesn't log me out from there either when the extension does.

Also not sure if it helps but the extension has me go through 2FA and I successfully complete that every time I log into the extension.

@johnjoemorgan
Copy link

johnjoemorgan commented May 18, 2021

Experiencing the same. Not useing 2FA. I have made sure all Firefox and other privacy settings are off for the HAS IP address. I call the extension, login and use the HAS page. I can go back a few moments or minutes later and I'm asked to log back in again.

When logged out HAS works as usual - no login required.

Notes

  1. I cannot logout of HAS manually from the extension
  2. When the HEADER is made visible the bug doesn't seem to appear.

@bokub
Copy link
Owner

bokub commented May 18, 2021

I'm sorry but I cannot reproduce this on my side, so I am completely unable to investigate and fix it 😞

  1. When the HEADER is made visible the bug doesn't seem to appear.

I highly doubt it, because I'm just cropping the window with CSS ! I don't see how it can influence anything related to authentication...

@johnjoemorgan
Copy link

Yep Agreed - seems that that was a false positive. It's back to asking for the login. Let me try again tomorrow on a different PC and see if I can get any clues in console for you.

@johnjoemorgan
Copy link

BTW - thanks for this. This linked with the Spotify/Spotcast custom component and the Mini Media Player card is a fantastic combo.

@1darklyte
Copy link
Author

sry I guess I didn't get an email for this chain. Testing now with the header enabled to see if that changes anything.

@1darklyte
Copy link
Author

1darklyte commented May 19, 2021

Well that took about 2 min for it to appear again haha.

https://prnt.sc/134kpqm

I was actually in the middle of checking another bug I found which when it happened again.

2nd bug is (and im not sure if this is by design or a limitation) but when I attempt to use the header (now that I have exposed it), it wont change the page but it does move a long the top navigation. https://prnt.sc/134khwv vs https://prnt.sc/134klu0

Also its now asked me to login 4 times in 6 minutes since I started testing again

@bokub
Copy link
Owner

bokub commented May 20, 2021

Thanks for the screenshot, but I still don't know how to reproduce it on my side, so I cannot do anything 🤷‍♂️

On my computer, I stay logged in 100% of the time, as it should be

@johnjoemorgan
Copy link

johnjoemorgan commented May 20, 2021 via email

@johnjoemorgan
Copy link

I think I have the cause. In Firefox about:preferences#privacy I had "Enhanced Tracking Protection" to STRICT. Changing this to STANDARD allows the HAS login to persist. Perhaps we can use the CUSTOM setting to avoid this.

Anyhows, hope this helps .

@bokub
Copy link
Owner

bokub commented May 20, 2021

That's it !

I tried to set the protection to "strict" and I the extension asked me to log in

Switched it again to "standard", and the extension was working again

Well done 👍

@bokub bokub closed this as completed May 20, 2021
@bokub
Copy link
Owner

bokub commented May 20, 2021

I've added a little explanation in the extension description for people who encounter the same problem

@1darklyte
Copy link
Author

I wonder if there is a way to do this without lowering security settings for the whole browser.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants