Print Page | Close Window

throw Login exception

Printed From: IdeaBlade
Category: DevForce
Forum Name: DevForce 2009
Forum Discription: For .NET 3.5
URL: http://www.ideablade.com/forum/forum_posts.asp?TID=1623
Printed Date: 05-Apr-2025 at 9:28pm


Topic: throw Login exception
Posted By: BruceKu
Subject: throw Login exception
Date Posted: 22-Jan-2010 at 1:08pm
I am running your ASPAuthentication sample.
I entered an incorrect password and in the following               code

protected override bool ValidateUserCore(ILoginCredential credential) {

// Base class calls Membership.ValidateUser, and returns t/f based on whether

// the user is authenticated. If not authenticated, we don't actually know why.

// The base class does not throw a LoginException if the user is not authenticated,

// so we do here.

bool isAuthenticated = base.ValidateUserCore(credential);

if (isAuthenticated) return isAuthenticated;

var members = Membership.FindUsersByName(credential.UserName);

if (members.Count == 0) {

throw new LoginException(LoginExceptionType.InvalidUserName, "Invalid username");

} else {

throw new LoginException(LoginExceptionType.InvalidPassword, "Invalid password");

}

}

the base.ValidateUserCore() fails as expected
 
It executes the "invalid Password"      throw new LoginException
 
RESULT: nothing happens and The Unhandled Exception function takes over.
 
1. What should be displayed ( I assume on the login page)
2. Why did it not intercept the error?
 
I ask as it is your code and I assumed it should work.
 
This is important to me as I am building a login page to test your devforce .
I also need access to roles later.
 
Hope you can help
 
Bruce


Replies:
Posted By: kimj
Date Posted: 23-Jan-2010 at 5:35pm
If you've added the code above to the sample "ASP.NET Membership and Roles" application, then you should see the LoginException returned in the LoginEventArgs when the login completes.
 
_entityManager.LoginAsync(credential, LoginCompleted, null);
 
private void LoginCompleted(LoginEventArgs args) {
  if (args.Error != null) {                   // args.Error will be the LoginException
    string errMessage = args.Error.Message;   // This will contain the exception message
    return;
  }
}
 
I'm not sure what you mean by the Unhandled Exception function ... but you should always check the Error property on the return arguments of any async call before trying to access the result.  If the LoginEventArgs provided to your Login handler doesn't contain the exception please let us know, or post additional code so we can diagnose the problem.

Posted By: BruceKu
Date Posted: 24-Jan-2010 at 3:45pm
I am not explaining myself well.
 
The code I entered in my last posting is straight out of your example. I have added no code to the example at all.
 
It comes from directory ...IdeaBlade Devforce\Learning Resources\100_Security\Samples\300SLV\CodeCs\
ASPNet Membership with Registration
 
It is part of the samples you installed on my C drive when DEvForce is being installed.
 
The code caught the error and caused the following line to be executed
 
throw new LoginException(LoginExceptionType.InvalidPassword, "Invalid password");

}

What I am asking is what does this code generate as a result?
 
I expected it to display a message on the 'View' and then exit normally.
 
Instead there was no display and the unhandled exception function(of the runtime in VS2008) caught the error and
terminated the program by stopping the execution and displaying the VS2008 error block.
 
I want to be able catch errors such as this and exit from the program normally. I expected this
code to do it and it didn't.
 
My question is how do I catch the error and exit using my own code for a normal program shutdown.
 
A wrong password should not cause the program to exit abnormally. It is.
 
As this is one of your examples I am hoping you understand this code better than me.
 
Hope that makes my question clearer.
 
Bruce

Posted By: kimj
Date Posted: 24-Jan-2010 at 6:39pm
My apologies.  For some reason I thought you were using another sample application and had added a sample code snippet. 
 
What should happen is that the LoginException you throw is caught by DevForce and turned into a LoginFault to be sent to the Silverlight application.  DevForce code in the Silverlight application then turns this fault back into a LoginException and tucks it into the LoginEventArgs.  In the sample, a MessageBox will pop up with the exception message.
 
When debugging in Visual Studio, VS will see this exception thrown and depending on your debugging options may stop you with the Exception Assistant.   There are several ways around this:
  •  Generally you can mark a type or member with the System.Diagnostics.DebuggerNonUserCode attribute to tell Visual Studio to ignore an exception thrown by your code.  Unfortunately, if you add it to the code here the problem still persists, so we likely also forgot to mark up the base class.  We'll open a bug report for this.
  • You can also have Visual Studio ignore this exception by adding "IdeaBlade.EntityModel.LoginException" to the Debug | Exceptions window.  Add the exception to the "Common Language Runtime Exceptions" list, and un-check the User-unhandled check box. 
  • You can also try out the LoginException functionality without the debugger (i.e., start without debugging).  This will show you how your users will see the feature, but isn't very useful since you probably do want to debug.
 
 
 


Print Page | Close Window