G
Gery D. Dorazio
The SQL Server 2005 security database that is installed for an ASP.NET V2.0
web app has the UserName and LoweredUserName in the aspnet_User table. It
appears that the only way the UserName is set is upon initial creation of
the user account. The MembershipUser.UserName is read only. It would make
sense that this is the case since the UserName is installed into the
authentication cookie which is passed between the client and server.
Changing the UserName while logged on would require updating the
authentication cookie.
It appears Microsoft did not allow changing the UserName because of the
above situation. However, the question for this news group is can the
UserName be changed if the authentication cookie is also updated or are
there other problems where the UserName is a factor which would cause a
problem with changing it?
Thanks,
G. Dorazio
web app has the UserName and LoweredUserName in the aspnet_User table. It
appears that the only way the UserName is set is upon initial creation of
the user account. The MembershipUser.UserName is read only. It would make
sense that this is the case since the UserName is installed into the
authentication cookie which is passed between the client and server.
Changing the UserName while logged on would require updating the
authentication cookie.
It appears Microsoft did not allow changing the UserName because of the
above situation. However, the question for this news group is can the
UserName be changed if the authentication cookie is also updated or are
there other problems where the UserName is a factor which would cause a
problem with changing it?
Thanks,
G. Dorazio