Hi,

I'm new to DNN and have just implemented a custom authentication module which authenticates against an existing mysql database and quietly creates a new user on the dnn MS 2005 db, transferring necessary data in the process. I have found that I can store a variety of values using the Personalization method:

DotNetNuke.Services.Personalization.Personalization.SetProfile("container", "key", "value")

It works fine and I can retrieve the data again with the corresponding GetProfile() method but I cannot find the data anywhere in the database (in the Profile or UserProfile table for example). Could anyone tell me how this method works and where the data is persisted. I am using DNN 6.00.00.

thanks

Tiernan

Tiernan

Hi Sebastian,

many thanks for your swift reply.

 I have done some further research and have found that the data is being persisted in a cookie.

 The reason I think is because DNN certain aspects of the user state are not updated after calling the UserController.UserLogin(...) method. I verified this by checking the UserController.GetCurrentUserInfo() which returned a null user directly after calling the UserLogin(...) method.

This agrees with SetProfile(...) behaviour which sets a cookie rather than persisting to the database when the current user is a null user (user id = -1).

Once the user is logged in and redirected to another page, SetProfile(...) works as expected, persisting data to the Profile table.

I suppose my question now is why the current user is not updated directly after  the call to UserController.UserLogin(...)  but seems to require a page reload to update its state to reflect the details for the newly logged in user?
Submit