Sunday 15 March 2015

authentication - Where to keep data about an authenticated user? -


I am working, which has been developed using some of the company's libraries / Kind frameworks.

Some MVC applications are already using - they are using form based authentication and they are not using the IPINist to store information about the user, rather it is a unity based approach, which Custom Iuser objects (originally kept in sessions) contain data. The web API app is going to be stateless (no session), just going to add some user related information to the authentication cookie (per request in Application_PostAuthenticateRequest has been retrieved.)

I'm a bit unsure To keep the data related to this user in the custom implementation of the IPINist (as I have done a practice) or using the IUser, Using the current approach Upryogon - per request served by Unity Using Life Manager.

What is a better approach than you?

If you keep track of users, try to use singleton classes per session, if you If the users logged in the session are about to create logs, then write it in a text file like the whitelist.

No comments:

Post a Comment