Implementing a Custom Membership Provider with slightly bizarre requirements?

I think it could work. We do #3 on one of our sites. Here is a chunk of code that we use to take care of it.To use this, create a login page (transparentlogin.

Aspx or something similar), make sure that the web. Config file allows anonymous access to this page, and put code like this in the page_load function for the transparentlogin. Aspx page: const string specialpassword = "ThisIsOurSpecialPasswordForBehindTheScenesLogin"; if (MobileNumberFoundInHeader()) { string username = GetMobileNumberFromHeaders(); // Authenticate the user behind the scenes System.Web.Security.

FormsAuthentication. SetAuthCookie(username, false); System.Web.Security. FormsAuthentication.

Authenticate(username, specialpassword); } else { throw new Exception ("Mobile Number Missing"); } Then, in the ValidateUser function in the MembershipProvider, make sure you do a check like this: public override bool ValidateUser(string username, string password) { const string specialpassword = "ThisIsOurSpecialPasswordForBehindTheScenesLogin"; bool ValidationSuccess = false; // If the password being passed in is the right secret key (same // for all users), then we will say that the password matches the // username, thus allowing the user to login if (password == specialpassword) { ValidationSuccess = true; } if (DoStandardUsernamePasswordVerification() == true) { ValidationSuccess = true; } return ValidationSuccess; } As for requirement #2, I'm a little confused. What exactly is an operator? I thought we were dealing with a mobile phone using a web browser to browse to a website.

Where does the operator fit into that? If the solution I propose above doesn't help, please post a response with more details about the Operator Tim.

I think it could work. We do #3 on one of our sites. Here is a chunk of code that we use to take care of it.To use this, create a login page (transparentlogin.

Aspx or something similar), make sure that the web. Config file allows anonymous access to this page, and put code like this in the page_load function for the transparentlogin. Aspx page: const string specialpassword = "ThisIsOurSpecialPasswordForBehindTheScenesLogin"; if (MobileNumberFoundInHeader()) { string username = GetMobileNumberFromHeaders(); // Authenticate the user behind the scenes System.Web.Security.

FormsAuthentication. SetAuthCookie(username, false); System.Web.Security. FormsAuthentication.

Authenticate(username, specialpassword); } else { throw new Exception ("Mobile Number Missing"); } Then, in the ValidateUser function in the MembershipProvider, make sure you do a check like this: public override bool ValidateUser(string username, string password) { const string specialpassword = "ThisIsOurSpecialPasswordForBehindTheScenesLogin"; bool ValidationSuccess = false; // If the password being passed in is the right secret key (same // for all users), then we will say that the password matches the // username, thus allowing the user to login if (password == specialpassword) { ValidationSuccess = true; } if (DoStandardUsernamePasswordVerification() == true) { ValidationSuccess = true; } return ValidationSuccess; } As for requirement #2, I'm a little confused. What exactly is an operator? I thought we were dealing with a mobile phone using a web browser to browse to a website.

Where does the operator fit into that? If the solution I propose above doesn't help, please post a response with more details about the Operator.Tim.

Cheers... yeah that's pretty much the conclusion I came to. Re: "Operators"... I mean the Mobile Phone Network Operators... e.g. AT&T, Vodafone, T-Mobile etc... – Eoin Campbell Jul 7 '09 at 10:07.

I think it could work. We do #3 on one of our sites. Here is a chunk of code that we use to take care of it.

To use this, create a login page (transparentlogin. Aspx or something similar), make sure that the web. Config file allows anonymous access to this page, and put code like this in the page_load function for the transparentlogin.

Aspx page.

Retailers should stop the risky "just in time for the holiday season" mantra when implementing technology solutions. I've seen this over and over in Retail IT sector and they seem to end up with more eggs on their face than success stories lately. Avid Finish Line (Online Shopper) & let me say first hand experience that site was absolutely horrendous...every link failed and timed out it was hellacious...The old site is just fine no need to change it.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions