In the last few days i crate a single sign on thorugh windows live, and it's already worked like a charm. However, now i should to make sure that the system not supported multiple login in differnts place (for example one user login in two or more computers)
Any experience about this? what should i do ?
creating a global asax application session? or umbraco already has this features...
Single SIgn on and Single user only
Dear All,
In the last few days i crate a single sign on thorugh windows live, and it's already worked like a charm. However, now i should to make sure that the system not supported multiple login in differnts place (for example one user login in two or more computers)
Any experience about this? what should i do ?
creating a global asax application session? or umbraco already has this features...
Thanks before
Hi Ridi,
I haven't tried it myself, but found a thread on the ASP.NET forum about disabling concurrent/simultaneous logins using membership providers:
http://forums.asp.net/p/1571186/3938613.aspx
There are loads of links and references on that thread... including:
http://www.eggheadcafe.com/articles/20030418.asp
http://geekswithblogs.net/Frez/articles/preventing-a-user-from-having-multiple-concurrent-sessions.aspx
... plus another ASP.NET forum thread on it here: http://forums.asp.net/p/1245799/2288756.aspx
Let us know how you get on!
Cheers, Lee.
Hi Lee, let me try it out first and no worry i will brief the result here :)
Cheers,
Ridi
Ridi,
I was just wondering if you were able to implement the single user with Umbraco. I am about to do the exact same thing for a subscription based site.
Thanks,
Justin
Hi Justin,
My solution is temporary, however here are the steps
Im creating a property in a member type, i called this as logged in flag with a datatype true/false
after that i create a login control that override onlogin event, by setting the property to true and create a Session for it
when they do a log off button you should override the also set the property to false and Sesions.abondon
furthermore you should aware the timeout of logged in, so you should take care of the Sessions timeout. Here are the two articles that good enough http://aspalliance.com/520_Detecting_ASPNET_Session_Timeouts and http://justgeeks.blogspot.com/2008/07/aspnet-session-timeouts.html
is working on a reply...