Authentication error on community - are you affected?

[#1]

@rongtw - I'm using FF 46.0.1 on Mac and I've never had any of these issues since it was previously 'fixed'.

[#2]

Mook , sadly Lithium,s fix for this error was to go back to Firefox 45

And is still here in FF46.0.1  windows 10 x64  ,, am just awaiting FF47 as it didn't give the error on the beta version

But it did have Flash player problems   hopefully fixed in release  

[#3]

Firefox 47 is now available, just updated.

[#4]

Thanks for the heads up, I have updated.

Just posted about 30 posts on a private board and did not receive any authentication or secure connection errors. Will keep my eye on it though.

[#5]

i have just updated   will see what happens

[#6]

And another cynic might say that since they aren't using FF never mind FF46, then it has naff all to do with the authentication errors

---

bobpullen wrote:

The window had been sat idle for a while and it's likely I'll have been browsing Community in other tabs.

Windows 8/Firefox 42.

Save

---

@LouisaMartin wrote:

Thanks @bobpullen going back and forth with Lithium on this. I'll send this to them and also send you on their response for a scan.

It worth remembering that there is some sort of timeout if you have an idle tab/window. When I tested it was around an hour here, but I'm sure @jaread83 knows and can confirm.

[#7]

You are correct @Anotherone, there is a timeout if you were to leave a the community open in your browser for an extended period of time. This is there as a security measure and can't be switched off in the system.

[#8]

@jaread83, what is the current timeout period, and are YOU able to adjust it ?

[#9]

Timeout is 60 minutes. The setting has some help text that goes with it though

Sets the amount of time (default is 30 minutes) a user session can be inactive before the user is automatically logged out. Be mindful when choosing this value. Setting it too high increases your security risk, but setting it too low can frustrate your users.

[#10]

Am I correct in thinking the max is 2hours @jaread83?

[#11]

IIRC that's what it is on Staging.

[#12]

---

@rongtw wrote:

Firefox still on 46 ,, no update yet

---

I've just had v.47 pushed to me.

[#13]

---

@Anotherone wrote:

IIRC that's what it is on Staging.

---

I remember we spoke about this before. I just checked the Staging environment and that is currently set to 60 minutes (same as here). I have just updated the timeout to be 2 hours here, let's see if that helps out some of you.

[#14]

@bobpullen, can you check whether there are any outstanding 'Flash player' problems with Firefox v47, as hinted at in - Reply#92

[#15]

I'd need to know what I was looking for. It seems to work on the few sites I've tried it, but I have it set to always prompt me for activation anyway.