Thanks for posting that. I finally figured out what to do the other night. Thats Pretty much the same thing as I did except i returned Username.

Works like a charm.

Chiming in as another user that needs the option to turn it off.

This token feature is a great workaround.  I need a little more power or flexibility though, and I am hoping that I do not need to modify the core in order to get this done.  The token works fine for the Registration page, but I have a custom Membership Provider that performs the following steps:

1. Replaces the Username with the e-mail address
2. Replaces the Display Name with the Username
3. Performs other business logic tasks

Using this token, it appears that although there is a different value for the DisplayName property, the core is automatically overriding it with whatever token you entered.  Does it retain the original DisplayName value?  If we attempt to use the DisplayName property directly from the UserInfo object, will we get the tokenized DisplayName, or the actual DisplayName? 

I need to use the DisplayName as an "Alias", much like the Live (passport) does.  This way, I can prevent the users e-mail address from getting displayed all over the place.  So, in a perfect world, I would love to be able to use the token or some other method to hide the DisplayName field on the registration and profile controls, but still display it as needed.  Since I am automatically handling this property in the Membership Provider, I do not have the same restrictions or requirements as most.

DNN sure has made it difficult to switch from a Username-based security model to an e-mail address-based one.  Whew!