Web authentication state – Session vs Cookie?
What’s the best way to authenticate and track user authentication state from page to page? Some say session state, some say cookies?
What’s the best way to authenticate and track user authentication state from page to page? Some say session state, some say cookies?
I’m trying to avoid the use of the Role Provider and Membership Provider since its way too clumsy in my opinion, and therefore I’m trying to making my own “version” which is less clumsy and more manageable/flexible. Now is my question.. is there an alternative to the Role Provider which is decent? (I know that I can do custom Role provier, membership provider etc.)
I have two sites, both on the same domain, but with different sub-domains.
site1.mydomain.com
site2.mydomain.com
Is there any built-in utility or helper to parse HttpContext.Current.User.Identity.Name, e.g. domainuser to get separately domain name if exists and user?
I’m struggling with how to set up authentication in my web service.
The service is build with the ASP.NET Core web api.
I have an application that used to use FormsAuthentication, and a while ago I switched it to use the IdentityModel from WindowsIdentityFramework so that I could benefit from claims based authentication, but it was rather ugly to use and implement. So now I’m looking at OwinAuthentication.
I am trying to set up Single sign on for 2 websites that reside on the same domain
Authentication cookies seem to timeout after a short period of time (a day or so). I am using Forms Authentication and have the timeout=”10080″ with slidingExpiration=”false” in the web.config. With that setting, the cookie should expire roughly 7 days after the user is successfully authenticated.
I am kind of successful by doing this in the Startup.Auth.cs file
Inside my corporate environment, I have IIS7.5 hosting both a Web API service and a separate website which makes calls into that service via the RestSharp library. Both are currently configured with Windows Authentication.