Daniel Nauck-2 wrote: > > Hello, > > another option is to use the internal ASP.NET authentification (forms > auth). > > There exist several providers for different databases, a PostgreSQL > implementation is available here [1]. > > Then you'll have full access to all required user, profile and session > data over the ASP.NET membership provider API. > > Daniel > > [1] http://dev.nauck-it.de/aspsqlprovider >
I know this project, thanks for the advice. It is very good and I plan to use it in the future. But, my intention for now is to use HTTP Authentication in combination with the ASP.NET FormsAuthentication. We have some clients, which are not capable to store the password within a formular login page. So I want to use the standardized authentification of HTTP. Now I can create the FormsAuthenticationTicket myself, with the logged in user and call FormsAuthentication.RedirectFromLoginPage() or FormsAuthentication.SetAuthCookie(). -- View this message in context: http://www.nabble.com/Authentification-tp24915849p24920077.html Sent from the Mono - ASP.NET mailing list archive at Nabble.com. _______________________________________________ Mono-aspnet-list mailing list [email protected] http://lists.ximian.com/mailman/listinfo/mono-aspnet-list
