Skip to main content

How to simulate token expiration if an user is idle on an AngulaJS using Bearer Token (OWIN and Katana)

In one of the project where I was involved I used token based authentication to secure a REST API endpoint -  bearer token. The setup was pretty simple, using OWIN and Katana on backend and AngularJS on the client side.
There is a great sample on GitHub, that can be used for learning purposes - https://github.com/tjoudeh/AngularJSAuthentication
This days a new requirement came from the client. The authentication session should expire if there is more than 30 minutes with no activity from client. By default when a token is issued it is available for a specific time interval. The value can be specified as below:
OAuthAuthorizationServerOptions oAuthServerOptions = new OAuthAuthorizationServerOptions
{
AllowInsecureHttp = false,
TokenEndpointPath = new PathString("/token"),
AccessTokenExpireTimeSpan = TimeSpan.FromMinutes(30),
Provider = new SimpleAuthorizationServerProvider(),
AuthenticationMode = AuthenticationMode.Active
};
This will works great in normal scenarios, but in our cases we had some problems.

The token is valid from the moment when is created for a specific time interval, in our case 30 minutes. Even if the user access the services using the token in minute 29, the token will expire and he will need to request a new token or to authenticate again entering his user and password.
An option is to use refresh token and track the last access time in a storage (cache, session or a database). The problems with this solution is:
-          We don’t have a cache yet
-          We don’t use session because we don’t need it
-          A solution with a DB would require an implementation effort and we need to see what is the impact over current DB

Before jumping to the solution that we thought, you should know that on the server there are no information that are stored related to token or user. The token is encrypted using machine key and can used only by the machine or machines that have the same machine key. The bearer token contains all the information related to user, from user ID to claims (current roles or actions that he can do on the server). Don’t forget that we cannot invalidate a bearer token because the server don’t track or store any kind of information related to it.

Based on the above information we measured how long it takes to generate a new bearer token on the server and the performance impact was minimal – with almost no additional resources.

Our solution:
  • On the ActionExecuted of an action filter generate a new bearer token after each call for authenticated users
  • Send this token to the client application
  • Persist this token on the client application
  • Use the token at the next call

The con of this solution is that we generate a new token at each call.
Below you can find the ActionFilter that generate a new token after each call using the claims from the previous call.
public class InjectNewTokenActionFilter : ActionFilterAttribute
{
    public override void OnActionExecuted(HttpActionExecutedContext actionExecutedContext)
    {
        base.OnActionExecuted(actionExecutedContext);

        ClaimsPrincipal principal = GetCurrentPrincipal(actionExecutedContext.ActionContext);
        if (principal == null)
        {
            return;
        }
        var newToken = CreateAuthTicket(principal);

        string token = Startup.OAuthBearerOptions.AccessTokenFormat.Protect(newToken);
        actionExecutedContext.Response.Content.Headers.Add("NewToken", token);            
    }

    private ClaimsPrincipal GetCurrentPrincipal(HttpActionContext actionContext)
    {
        ClaimsPrincipal principal = actionContext.RequestContext.Principal as ClaimsPrincipal;
        return principal;
    }

    private AuthenticationTicket CreateAuthTicket(ClaimsPrincipal oldPrincipal)
    {
        ClaimsIdentity identity = (ClaimsIdentity)oldPrincipal.Identity;
        AuthenticationProperties props = CreateAuthenticationProperties();
        AuthenticationTicket ticket = new AuthenticationTicket(identity, props);
        return ticket;
    }

    private static AuthenticationProperties CreateAuthenticationProperties()
    {
        AuthenticationProperties props = new AuthenticationProperties(new Dictionary<string, string>
        {
            {
                "client_id", string.Empty
            }
        });
        return props;
    }
}
And the JavaScript code that can be used on client side to update the bearer token for each response. This was done by intercept the http response.
var Services = Services || {};
Services.authInterceptorService = function ($q, $injector, $location) {
    ...
    var response = function(response) {
        //Sample
        IF(heather new token is set)
{
       SET NEW VALUE TO globalObjWhereTokenisStored.token = header(‘NewToken’)
}

        return response;
    }

authInterceptorServiceFactory.response = response;

    return authInterceptorServiceFactory;
};

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

What to do when you hit the throughput limits of Azure Storage (Blobs)

In this post we will talk about how we can detect when we hit a throughput limit of Azure Storage and what we can do in that moment. Context If we take a look on Scalability Targets of Azure Storage ( https://azure.microsoft.com/en-us/documentation/articles/storage-scalability-targets/ ) we will observe that the limits are prety high. But, based on our business logic we can end up at this limits. If you create a system that is hitted by a high number of device, you can hit easily the total number of requests rate that can be done on a Storage Account. This limits on Azure is 20.000 IOPS (entities or messages per second) where (and this is very important) the size of the request is 1KB. Normally, if you make a load tests where 20.000 clients will hit different blobs storages from the same Azure Storage Account, this limits can be reached. How we can detect this problem? From client, we can detect that this limits was reached based on the HTTP error code that is returned by HTTP