Hello Shimon,
As other member has mentioned, you need to first enable
"anonymousIdentification" and also set those certain profile properties to
"allowAnonymous" accessing. And as for the Login control's "LoggedIn"
event, it is specific to the login page scope which can let us do some
operation on the page to update the UI after the user has clicked login
button and successfully loggedin. However, that that event time, the
HttpContext.User(or the profile service identity) is still not updated yet,
so this event is not quite suitable for your task.
Based on my research, if you want to adjust some profile properties after
the user has loggedIn(change from anonymousIdentity to a valid
authenticated identity), you can use the ProfileModule's "MigrateAnonymous"
event which will get fired after the user has loggedIn and this event is
specific to profile service. You can migrate some profile properties' value
from original anonymous identity to the authenticated identity:
#ProfileModule.MigrateAnonymous Event
http://msdn2.microsoft.com/en-us/lib...ofilemodule.mi
grateanonymous.aspx
Hope this helps.
Regards,
Steven Cheng
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Get Secure!
www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
