Security :: Login Control On Master Page Doesn't Disappear
Feb 1, 2011
I have developed a website wherein login control is placed on the master page and property - Hide when logged in is set to true, so that when a user logs in this control disappers.
However, my page doesn't display such behaviour, though I could login successfully.
I'm using Microsoft Visual Web Developer 2010 Express. I have created a web page. It opened fine. I then added a table to my site.master page and add some text and images. Everything compiles and runs fine until I hit the Login button. I then lose all my images, which are stored in an "Images" folder in the Web Page path. I have tried giving allow users="*" in the authorization section of the web.config file. It changed nothing. I must also tell you that I moved the Login control into the table to position it better. I do not understand how that would affect the images though.
I have a strange problem on a website with security user & roles active on it, the thing that happens is that if a user hit's the site defaults page he is auto logged in as another user? I have made my site structure like this : On my master page
A loginview with a loggedin & anonymous template on it, when I user is logged in he gets his name & logout button, otherwise a username login textbox and button. A menu that is build from a database depending on the rolde of the auth. user Site structure ROOT
default.aspx account.aspx /Level A dir (only for A role users) /Level B dir (only for B role users) /Public dir (everyone)
I have created a "fill number page" & a "login" page, it works well until the validation add on the "fill number page". Though login name and password are right in the "login page" but stand still don't move on to the "fill number page". While deleting the "<asp:CustomValidator ID="Validator1" ...="Number" />", it works fine as usual!
i am having login.aspx as start up page (In Admin Panel) . In login Page i am giving a value to session and i am checking that value in all pages page_load event, if expires it will redirect to login page. Consider if that session doesn't expire, at that time if i try to enter into page inside Admin Panel directly from website for first time, it should redirect to login.aspx but it will take me to that particular page (Since Session doesn't expire).
I have searched hours but fail to solve my problem. I have got the following issue,
I have created a login page on my web based application, which works fine, I want if user manually types different page or bypass the login page then it should redirect to the login page.
The problem is I have use Master Page and when I do the following code; it went into the loop, because when page load the session value is null.
How I can exclude my login.aspx and Error.aspx pages from this Check.
I have created a master page with a Login Control, however it does not authenticate, the page will refresh and display the anonymous template of the LoginView control. LoginView control works if I place in into ContentPlace holder.
It worked just fine untill this week, but now it fails to login.
the odd think is that it do login from localhost, but when trying to login through the profuction site it fails to login. this is happens to all users.
When user login into my application,the note saying that Welcome,Joe is show.But,when user try to input something into web page (such as fill in the text box),the LoginName1 that refer to "Joe" is suddenly disappear.Why this happen?
I want to put a Login Control and a Create User Control on the same page.. just wondering, before I start am I going to run into any problems by doing this?
I was reading some tutorials on Internet and Go through some Scott articles. I learn how to make form security with different types and roles. Now I wanted to know is it possible to secure asp.net control as per user login or just web page and directories.
I have created a login page using the login control provided by the visual web developer and set up all the accounts and roles using the web admin tool. Everything works fine if I run the page within the developer but when I host it on IIS, The login does not work. It shows the invalid password message from the login control.
I wanted to know how to add the feature- that user should be redirected to an error page where the error will be display, upon entery wrong username/password when trying to login through an asp.net login control?
1. how to redirect the user to an error page upon entering wrong username/password (from a login control which is placed on master page)?
2. how to pass the error to the error page so it can be displayed there?
I am using Visual Studio 2008 Express and created a login page using the ASP.net web site Adminstration tool security to generate users and passwords.
After login, a new page appears. I have a button to go back to the login page to allow a user to relogin. When I try loging in again as a different user or the same, I get an error saying the resource that I am looing for was not available.
I have a button on the page after login (one this one page will occur) and I am using on on click event to do the following:
After clicking on this button, the Login page appears again. How can I release everyting to allow it to work like when I first open the application.
This is the error message I get:
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /MyFirstSite/default.aspx
Version Information: Microsoft .NET Framework Version:2.0.50727.3615; ASP.NET Version:2.0.50727.3618
I am doing a simple secured site using the login control. I would like users to be redirected to their dashboard page once they log in, but after that if they choose to browse I do NOT want them redirected based on their login status. I am using the generic template provided in VWD with the basic login setup in the template including the tabbed ASP menu control - nothing fancy, nothing custom. This is intended to be something very simple and quick. Here is the code I am using for the page load...
[Code]....
So if I do this code WITHOUT the "IsPostBack", logged in users are always redirected to their dashboard and cannot see the hompage. However with that IsPostBack test, the redirect after initial login doesn't work.
I know this is extremely basic and simple, but I am restarting with this stuff after a year away, and I need a nudge.
I have very simple validation on the aspx page (highlighting not valid textbox), and it works perfectly. But when I try to work with this page using MasterPage, I've got an error - "Object reference not set to an instance of an object." (with reference to the line "aControl.BackColor=Drawing.Color.White" - underlined).