MVC 5 user data available on all pages - asp.net

Question

Basically I need user data to be available on all pages in the site.
I need to display some user properties in the layout, like:
[Username], [FirstName], [LastName], [Email], [IsEmailVerified],
[Phone], [LastLoginDate], and 4 more properties...
But, these aspects need to be considered:
No use of Session (I disabled it in my application).
No database interaction on each request in order to get those user properties - I want to get them properties once and store them somewhere available.
I use Forms Authentication.
Now, from a little search I made, I found this article from 2008, posted by Microsoft, about Forms Authentication: Storing Additional User Data in the Ticket, and Using a Custom Principal.
I think this is the closest approach, because now I use User.Identity.Name to get only the [Username] stored in the authentication ticket, and I love using it because it is quick, available and simple.
But I also have a few questions that bother me with this approach:
This was posted in 2008, is it still relevant for 2017? is there something better and new today?
As you can see above, I have quite a bit user properties that need to go into the auth cookie, and as I read - a lot of user data in the auth cookie is not reccomended...
Thanks for the helpers.

Answer 1

Yes, it's still valid. Although people will tell you that newer approaches exists that involve claims and you should possibly considef the new Identity subsystem, the old good forms authentication is still one of viable options.
As for "lot of data", it's just one of shortcommings of the forms module, it doesn't handle multiple cookies, thus, you are constrained by the 4kb limit of a single cookie. Considering the encryption and signing, this makes much less data available in the custom data section of the cookie. But still, it should still be enough to have a simple serialization of like 10 attributes.
If you want to make a half of a step forward, you can just switch to the session authentication module, a benefit is that it is based on claims plus it supports large user data (as it automatically splits the data into chunks). I've blogged on that some time ago
http://www.wiktorzychla.com/2014/11/forms-authentication-revisited-for-net.html
A snippet from this approach
var identity = new ClaimsIdentity( "custom" );
identity.AddClaim( new Claim( ClaimTypes.Name, txtLogin.Text ) );
var principal = new ClaimsPrincipal( identity );
principal.AddClaim( new Claim( ClaimTypes.UserData, "whatever goes here" ) );
SessionAuthenticationModule sam =
FederatedAuthentication.SessionAuthenticationModule;
var token =
sam.CreateSessionSecurityToken( principal, string.Empty,
DateTime.Now.ToUniversalTime(), DateTime.Now.AddMinutes(20).ToUniversalTime(), false );
sam.WriteSessionTokenToCookie( token );