Forms Authentication – Manual Authentication

F03I0043

I’ve had several occasions in the past where I’ve needed to do my own authentication or I’ve needed to add some additional methods to the authentication process.

As easy as Microsoft has made the authentication process, you might think that in order to  manually authenticate you’d need to write all of your authentication code manually.  But nothing could be farther from the truth.

In fact, most of the time all you need to do is trap an event handler in the existing login control.

A couple of years ago, I was asked to create a login page that used a web service to authenticate the user.  I also needed to add another form field to the login screen, so it became obvious that to do this I’d need to turn the login control into a templated control.

Once this was done it was a simple matter to trap the click event of the login button, authenticate against the web service, and then set the authentication cookie for ASP.NET.

Since I can’t show you how to authenticate against the service–your implementation will almost certainly be different–we will skip that section.  But to set the cookie, all we need to do is to revert to the ASP.NET 1.1 way of setting up the login.

if (Request.QueryString["ReturnUrl"] != null)
{
    FormsAuthentication.RedirectFromLoginPage
        (m_tbUsername.Text, persistentCookie); } else { FormsAuthentication.SetAuthCookie
        (m_tbUsername.Text, persistentCookie); Response.Redirect("~/"); }

The first line checks to see if there was a Return URL specified.  If there was we can use the RedirectFromLoginPage API.  Otherwise, we need to set the Authentication Cookie manually and redirect on our  own.

The persistentCookie parameter is true if we want the user to always be logged in.  Otherwise, the login is for the session.

Related Post

  • Authentication – Assigning Permissions to RolesAuthentication – Assigning Permissions to Roles Now that we’ve assigned roles to our users, we need to assign permissions to the roles. The easiest way to do this is through the web.config file, which will allow us to control which pages the...
  • Determine The Role of a User in ASP.NETDetermine The Role of a User in ASP.NET There are several controls that allow you to display content based on the role a user is in, including: - LoginView - LoginStatus And the web.config file allows us to control which pages can ...
  • ASP.NET Assigning a Role to a UserASP.NET Assigning a Role to a User Another function that is not supplied by one of the existing controls in ASP.NET is the ability to assign a user to a role.  For this, we will need to resort to using the APIs. Since we ca...
  • ASP.NET Authentication – Multiple Domains w/ Same ApplicationASP.NET Authentication – Multiple Domains w/ Same Application In our series about ASP.NET authentication so far we’ve covered all the rather normal cases where you’d want to have the ability to log into different domains attached to the same application.&#...
  • Facebook App using DotNetNukeFacebook App using DotNetNuke Yeah, I know.  It has been a LONG  time since I posted anything.  I’ve been busy. One of my recent projects brought up something I think you may be interested in so I thought I’d post about ...
  • Salman Butt

    Why cant you just show us the code for authenticating against the service as well? It doesnt matter if our implementations are different – we can at least the get the feel of what exactly the entry is about. Please post some sample authentication code as well as how to tap into login control events?