Skip to main content

ASP.NET custom forms authentication - Part I


Forms authentication is generally used in internet facing applications. ASP.NET provides easy to use Membership Providers, Role providers etc. But some times we do need to right custom authentication code. That is what we are going to discuss today.


Let us start with points to be considered:  
Note: I am going to use cookie for state management.


We need cookie for forms authentication.
We need cookie for session management.
We need to clear and abandon the session on logout. 
We need to clear authentication ticket too.


Web.config
Here we have set the name for the authentication cookie. We have set the loginUrl - URL of the login page. We have set a defaultUrl - URL of the page where the user will be re-directed after login.


for other attributes please visit this MSDN page.


Authentication
On (say) login button click write this code


    protected void btnLogin_Click(object sender, EventArgs e)
    {  
         if(Valid(userid,password))
         {
             if (Request.QueryString["ReturnUrl"] != null)
      {
        FormsAuthentication.RedirectFromLoginPage(UserID, false);
      }
      else
      {
        FormsAuthentication.SetAuthCookie(UserID, false);
        Response.Redirect("~/Pages/Home.aspx");
      }
         }
         else
         {
            Do something....
          }
    }


Here Valid() is the custom function which validates the user. UserID has been passed RedirectFromLoginPage and SetAuthCookie functions as this will be used to set the user in context.


LoginStatus control (for logout)
protected void UserLoginStatus_LoggingOut(object sender, LoginCancelEventArgs e)
{        
  Session.Clear();
  Session.Abandon();
  FormsAuthentication.SignOut();
}


In the next part we will look deeper into this. This post was just to get the work done :D. ( Next Article - Part 2)


Hope this will be helpful. Happy Coding!!!

Comments

Popular posts from this blog

Laravel XAMPP MySQL artisan migrate install error mysql.sock

In my previous post I wrote about setting up Laravel 4 on Mac with XAMPP . When I tried to use migrations (using artisan) I faced some issue. I will also post about Laravel migrations soon.    php artisan migrate:install Error :                                                     [PDOException]                                       SQLSTATE[HY000] [2002] No such file or directory                                              Solution : We need to tell artisan which mysql we want it to use. For this to work we need to porivde it with mysql.sock which we want it to use. So change your database settings like this: 'mysql' => array( 'driver'    => 'mysql', 'host'      => 'localhost',     'unix_socket' => '/Applications/xampp/xamppfiles/var/mysql/mysql.sock', 'database'  => 'wedding', 'username'  => 'root', 'password'  => '', '

Add (Drop) a new article (table) at publisher in merge replication

Let us add the article using the GUI first. First of all create the table on publisher database. Now right click on the publisher and select properties from the menu. Click on articles. Uncheck the - "Show only checked articles in the list" checkbox, in order to see the newly added table. Select the table as shown in the figure below. Press ok The article has now been added to the publisher We now need to recreate the snapshot Right click the publication and select – “View snapshot agent status”. Click start to regenerate snapshot. Now right click on the subscription (I have both on same server you may have on different servers) and select “View synchronization status” Click on start on the agent. The schema changes will propagate to the client if you have "Replicate schema changes" property set to true in the publisher.

Check SQL Server Job status (State) using sp_help_job and xp_sqlagent_enum_jobs

This article is about checking the status of a SQL job. In our work place we have lot of SQL jobs. These jobs will run whole day and are business critical. They will load the data and generate extracts which will be used by business people. Thus, it becomes quite essential to support the system efficiently so that the job finishes in time and as desired. Also, while designing a new system sometimes we need to check the dependency of one job over another. In such scenario we need to check whether a particular job has finished or not. All this can be achieved in SQL Server by using the procedures:- sp_help_job xp_sqlagent_enum_jobs Note: xp_sqlagent_enum_jobs is an undocumented proc inside of sp_help_job and is used extensively to get SQL agent job information. sp_help_job: This procedure gives some insight into the status, and information, about a job. This stored procedure provides information such as last start time, job status etc. Syntax sp_help_job { [ @job_id= ] jo