In my asp.net application I user Microsoft Membership to manage site access security and find the time saved into LastLoginDate is ahead of local time (Eastern Time Zone) 3 hours. What is wrong with it and how to ajust it to local time by application system only such as changing some properties od application?
I set these setting below at the Web.config of my site And it still return me to the loginpage after about 20 mins I checked the Properties of the site at IIS and the time out is 660 However at the properties of the defaultWeb it's not 660 since it will influence all the sites and that I don't want
When I tested my ASP.net page on the local host, the time came out exactly right. But when I uploaded everything and tested it out on the internet, it was 3 hours behind -TimeLabel.Text = Now.ToShortTimeString It's 7:44AM here, but it shows up as 4:44AM.
I want to calculate total hours with minute and display date, IN timing, Out timing of employee and total work between these time and I'm using vb.net 2005 and sql server 2005 ...
whenever I replace a master page on my site the pages load after a few hours(1-2) and only after that the site returned to work as normal.. I dont use VS "open web site" from the web method, instead I download the page I want to change (using flashfxp for instance), make my changes and upload it back. I do this process because every now and then the VS stuck/not responding/think long time. he master pages I change are used by few thousand of pages in the site, my thought is that whenever I change a master all the site get rebuild and therefor the long loading time..
for Business needs i am planning to increase the session timeout to 2 hours(120 min) in one application, i am using sql server session state. if i increase to 2 hours of session time out, how it will effect the performance of application and web server.
i was just wondering how one would approach creating a link that would be active for 24 hours for a user... ie i have in the db a time of confirmation and then wanted to make a download active for them for 24 hours and deactivate it post then.
I have a server that gets it time reset to 7 hours in the past. When this happens forms authentication no longer works.
When I resync the time with the server time it works again.
What could be causing this? It is actually and issue for me more so then changing the time, because I don't think it will be possible to keep all the clients and the servers in sync.
is my session related tag in web.config file but most of the time if i idle 20 minutes then its automatically timedout and went to my login page, is there any solution ?
I am trying to "marry" them up together. so lets say if session timeout is 2 minutes and same with forms authentication.
I want the ability to redirect the user to a page. (no, not using meta tags or anything to refresh the page) on any navigation after the time out.
Sure, create a control and drop it in the master page. All good
but there doesnt seem to be a way to determine if a user was logged in and if so... do what I need to do (i.e Signout and redirect) but it should not impact users who have not logged in.
The only time objects are being added to the session is when the User has logged in. infact the only object in session is a Custom User object.
I have 3 seperate applications (under the same domain) for which I use Forms authentication with single sign-on.
The 3 applications have different session timeout periods. I was on various articles that when we use forms authentication and specify the loginurl in the <Forms> tag in the web.config, it should automatically get redirected to the login page, when the session timesout. But in my case, it doesn't happen, I think because of different timeout values.
I have a web app containing a silverlight application. How do I keep the ASP.NET session / Forms Authentication alive when the user is using the silverlight application?
I simply want to display a message on the login page when the user is automatically redirected there after requesting a page that they were logged in for but their session has now expired. So essentially if the user was working but stepped away for a lunch break without logging out I want the system to tell them why they were sent back to the login page.
Something like "You have been idle for too long so you must log back in".
This has to be easy I am just running into a wall here. I thought about getting the original ticket and reading the expiration date but I'm a little lost.
We're using ASP.NET and IIS 6.0. I realise that the definitions of applications, websites and virtual directories are ill-defined in IIS 6, and changed a lot in IIS 7. However, I'm stuck with IIS 6.0 for now.
We have a single web site defined in IIS, and a number of separate sub-sites in Virtual Directories.
The scheme looks like this:-
[URL]
[URL]
site1, site2, ... are virtual directories in IIS 6.0, under the "Default Web Site".
I need to use ASP.NET sessions and forms authentication in most of these sites, and I don't want them to share authentication data or session information at all.
Both the mechanisms currently depend on cookies. However, the cookies created by default use the same name, and have a path of "/" in the browser, meaning the sites' cookies will clash with each other.
Without changing the default name for each cookie, how can I enforce separation between my sub-sites? Do I need to change the virtual directories for IIS 6 "Applications"? Or is there some way in code to enforce a more limited scope for the cookies?
Using VS 2010 RC, VB, and Forms authentication to allow access to the site, depending on the login rights of a user, I want to turn on and off access to certain pages. I can turn on and off buttons to access the pages, but a user can type the page into the url, and it will still go to them.