Hi gdycus,

Taken from the v4.7.1 release notes:

We've made the dreaded lock screen disabled by default by ensuring that Umbraco auto-renews login as long as the browser is open. The lock screen can be enabled via a new setting in umbracoSettings.config called /settings/security/keepUserLoggedIn which should be set to false.

I'll update the notice on the project page.

Cheers, Lee.

Hi,

I upgraded my Umbraco 4.7.1.1 instance to Umbraco 4.7.2

Although the 'keepUserLoggedIn' is set to 'true' I still get the 'dreaded' lockscreen.

In my web.config file, the 'umbracoTimeOutInMinutes' is set to '20'. Should I deleted this settng?

Thanks for your advice,

Anthony

Hi Anthony, (apologies for the delay, I'd been away on holiday)

I wouldn't recommend deleting the "umbracoTimeOutInMinutes" AppSetting - I have no idea of the impact of that.  Instead you could increase it to something more significant?  For my local development, I set it to be 200.

Seems strange that the "keepUserLoggedIn" setting isn't working for you. Hmmm

Cheers, Lee.

I am sorry to say The setting keep user logged in just does not function! Either with the setting true, which makes sense, nor with the unlogical setting false as stated here before! I am fed up with this behaviour and start to loose any confidence in Umbraco. If I have 2 instances active then the timeouts of the 2 instances influence each other! They are not separated by putting them in another namespace. Terrible!

Hi Leo, sorry to hear about your frustrations.

Are the 2 instances on your local development machine? (e.g. both accessed on "localhost"?)

If so, then the issue might be due to the cookies for localhost, as they contain the timeout duration value - so when one would expire, the other instance would read the same cookie and also log out.

So that means the choice of how you are using cookies is wrong! At least identify the instance the timer is connected to not just some global localhost!!! 

Still it leaves open the question why the keep logged in does not work, with only one instance running!

Hi Leo,

I'm not sure why the keepUserLoggedIn setting is not working for you - which version of Umbraco are you using?

(Personally I tend to increase the umbracoTimeOutInMinutes setting to 200+ minutes.)

As for the logic itself, if you have a better alternative, I'm sure the core team would like to hear it.
Feel free to raise any issues on the tracker: http://issues.umbraco.org/issues/U4

Thanks,
- Lee

Sorry I am new to Umbraco. It was suggested to me to use this because of its simpleness. Now I find it is not so simple and it looks very sensitive to doing things wrong, as beginners do! Still I like to keep myself on track and overcome these troubles.

I have no idea why it is not working and I will try the other setting you mentioned to get me out of frustation!

I had downloaded the V7.0.1, but now I am back at v6.1.6 because there are almost no packages for a starter to use. Also the videos are not in that format of v7. I might later upgrade when the v7 has grown up! I hope you can confirm this is a better way to start learning Umbraco!

Found it  umbracoTimeOutInMinutes . Hope this works! It does!!!!!. Now I have set this value in web.config to 300 for all my instances. This is comfortable when working with an example and copy bits and pieces from one to the other.

No worries Leo - I've been there too! :-)

With the multiple development instances on "localhost", (and cookie conflicts), Umbraco wasn't really designed to deal with that scenario - it is expecting 1 hostname per instance.
Currently this might be seen as an edge-case ... and may be fixed in future if there's a demand ... (but that doesn't help you right now)

With the keepUserLoggedIn not working - again, I'm not sure, it could be a bug - I haven't investigated myself.

As for versions, v7 is still new - like you say many packages don't work on it. Over time there'll be more resources/tutorials for v7 ... but for right now, v6 is a more stable option.

Good luck with your project(s) and feel free to ask any questions on the forum.

Cheers,
- Lee

@Leo - yup, the umbracoTimeOutInMinutes setting is in the <appSettings> section of the Web.config.

is working on a reply...