Custom Client not persisting in subsequent requests

Questions
1

I am adding a custom client after okta authentication flow, but it is getting lost in subsequent requests. How to ensure it is not getting lost.
Below is my startyup.cs code and default page where authenticating the user

		app.SetDefaultSignInAsAuthenticationType(CookieAuthenticationDefaults.AuthenticationType);

        app.UseCookieAuthentication(new CookieAuthenticationOptions());

        app.UseOktaMvc(new OktaMvcOptions()
        {
            OktaDomain = ConfigurationManager.AppSettings["okta:OktaDomain"],
            ClientId = ConfigurationManager.AppSettings["okta:ClientId"],
            ClientSecret = ConfigurationManager.AppSettings["okta:ClientSecret"],
            RedirectUri = ConfigurationManager.AppSettings["okta:RedirectUri"],
            PostLogoutRedirectUri = ConfigurationManager.AppSettings["okta:PostLogoutRedirectUri"],
            GetClaimsFromUserInfoEndpoint = true,
            Scope = new List<string> { "openid", "profile", "email" },
        });

Code that uathenticates user , adds a custom claim from db

		if (!Request.IsAuthenticated)
        {
            HttpContext.Current.GetOwinContext().Authentication.Challenge(
                new AuthenticationProperties { RedirectUri = "/" ,AllowRefresh=true,IsPersistent=true},
                OpenIdConnectAuthenticationDefaults.AuthenticationType);
        }
        if (Request.IsAuthenticated)
        {
            
            var userName = HttpContext.Current.GetOwinContext().Authentication.User.FindFirst("email").Value;


            var profile = _securityBll.Value.Profile_SelectByUserName(userName);
            if (profile == null)
            {
                //navigate to error page
                return;
            }
            
            var IdentityString =JsonConvert.SerializeObject(profile);

            var claims = new List<Claim>
            {
                new Claim("ImpIdentity",IdentityString)
            };
            claims.AddRange(HttpContext.Current.GetOwinContext().Authentication.User.Claims);
            var visionIdentity = new ClaimsIdentity(claims, OpenIdConnectAuthenticationDefaults.AuthenticationType);

            HttpContext.Current.GetOwinContext().Authentication.User.AddIdentity(visionIdentity);
           
            Thread.CurrentPrincipal = HttpContext.Current.GetOwinContext().Authentication.User;
2

Can you explain what your use case is?

3

Use case here is - once authenticated with okta successfully, application validates the user (email from okta) against the database and if successfull, add it to identity created by Okta middleware. This identity is used in all subsequent pages to retrieve various information about the user where ever required.

Issue here is identity after okta has 37 claims. I added a custom claim that has basic user details in the form of string.
But in subsequent page requests, the custom claim is not available, only 37 claims are available.