Support us .Net Basics C# SQL ASP.NET ADO.NET MVC Slides C# Programs Subscribe Buy DVD

Using fiddler to test ASP.NET Web API token based authentication

Suggested Videos
Part 20 - ASP.NET Web API token authentication
Part 21 - ASP.NET Web API user registration
Part 22 - Using asp.net identity with Web API

In this video we will discuss how to test ASP.NET Web API token based authenticationthe using fiddler. This is continuation to Part 22. Please watch Part 22 from ASP.NET Web API tutorial before proceeding.

In our previous video we have registered a new user with the following email address and password. The username is also the email address.
Email : test1@test.com
Password : Test123!



Now let's use fiddler and generate the access token using the above username and password. Use the Composer tab in Fiddler to compose a request. Fiddler configuration is shown below.
  • Issue a POST request to /token 
  • In the request body include username and the password. 
  • We also need to set grant_type=password. This indicates that we are presenting password for acquiring access token.
Token generation in ASP.NET Web API



With the above configuration in place, click the Execute button in Fiddler. Notice we get the access token back. You can also see when the token is issued and when it expires. 
web api create token

Now let's understand how the access token is generated.
The code that generates the access token is provided by ASP.NET Web API out of the box. To see this code open the file "Startup.Auth.cs" that is present in App_Start folder. Notice in the ConfigureAuth() method
  • An instance of OAuthAuthorizationServerOptions is created
  • The /Token end point to which we have posted username and password is specified in here
  • The token expiry is specified using AccessTokenExpireTimeSpan property. In this case the token expires 14 days after it is issued. You can change this to meet your application needs.
  • The Provider property is initialised with a new instance of ApplicationOAuthProvider class. This class has GrantResourceOwnerCredentials() method which verifies if the provided username and password are valid. If valid an access token is issued. The token is generated when context.Validated(ticket) method is called.
Now let us see how to call EmployeesController and retrieve employees data.

If we issue a GET request to http://localhost:61358/api/employees we get 401 Unauthorized error. Since the EmployeesController is decorated with [Authorize] attribute, the request needs to be authenticated. So with every request we have to send the Bearer token using Authorization header as shown in fiddler below.
fiddler bearer token

In our next video we will discuss implementing the Login page for the sample application that we have been working with in this series.

ASP.NET Web API tutorial for beginners

4 comments:

  1. where is database is created or by default its made of not?

    ReplyDelete
  2. i got 400 bad request error while generating token? what about database in Oauth2 token generation or verifying?

    ReplyDelete
  3. The last step that in Fiddler http://localhost:1656/api/employees. Specify the Token i.e Authorizatio : Bearer. which token is that from where i will get that token number to give in.

    ReplyDelete
  4. I replaced [BasicAuthentication] attribute from previous tutorials with [Authorize] to avoid the base64 encoding. Now I am getting this error:
    Under RFC2616, HTTP/400 responses will not be cached regardless of what caching headers may be present.
    HTTP/1.0 Expires Header is present: -1

    Legacy Pragma Header is present: no-cache
    !! WARNING: IE will only respect a Pragma: no-cache Response Header on a HTTPS response. Using this value on a HTTP response has no effect.

    HTTP/1.1 Cache-Control Header is present: no-cache

    This response contains neither an ETAG nor a Last-Modified time. This will prevent a Conditional Revalidation of this response.

    ReplyDelete

If you like this website, please share with your friends on facebook and Google+ and recommend us on google using the g+1 button on the top right hand corner.