REPOST: bug in Forms Authentication
- From: Tim_Mac <timmer3@xxxxxxxxx>
- Date: Wed, 12 Nov 2008 01:35:39 -0800 (PST)
hi, i tried posting this last month but got no takers, trying again!
i have a minor problem where some users log in with capital letters
for their username, which looks bad when displayed on screen and also
causes discrepancies in some user activity logs maintained in the
database, e.g. "JOE BLOGGS Login" and "Joe Bloggs Login". in an
attempt to standardise the username case, i tried to read the correct
username from the database, this code used to work fine:
protected void Login1_LoggedIn(object sender, EventArgs e)
{
// find the Membership User
MembershipUser u = Membership.GetUser(this.Login1.UserName);
if(u == null)
throw new Exception("Could not locate user account for
" +
this.Login1.UserName);
// use the correct username case (from the aspnetdb database)
for the
login cookie
FormsAuthentication.SetAuthCookie(u.UserName, true);
}
but there seems to be a behaviour change since asp.net 3.5, this code
no longer works as expected, Membership.Username now returns the same
case as was submitted by the user, so the Username property is
actually not coming from the database at all. surely this can't be
'by design'?? can anyone confirm if this is a bug, and/or suggest a
workaround?
many thanks
tim
.
- Prev by Date: RE: ASP.NET User.Identity.Name value after a domain username change
- Next by Date: Impersonation?
- Previous by thread: RE: ASP.NET User.Identity.Name value after a domain username change
- Next by thread: Impersonation?
- Index(es):
Relevant Pages
|
