Running web application locally as a predefined user using OWIN Middleware

01 Mar 2015 • Visual Studio • IAM

It is quite common that we sometimes need to run the application without all the identity server redirection dance at development time. It is possible to assign common identity to all the users running the application locally as follows.

Create a custom authentication middleware as follows.

public class LocalAuthenticationMiddleware : OwinMiddleware
{
    
    public LocalAuthenticationMiddleware2(OwinMiddleware next) :
        base(next) { }

    public override async Task Invoke(IOwinContext context)
    {
        var response = context.Response;
        var request = context.Request;

        response.OnSendingHeaders(state =>
        {
            var resp = (OwinResponse)state;

            if (resp.StatusCode == 401)
            {
                resp.Headers.Add("WWW-Authenticate", new[] { "Basic" });
                resp.StatusCode = 403;
                resp.ReasonPhrase = "Forbidden";
            }
        }, response);

        // use this identity only if running locally
        if (request.Uri.IsLoopback)
        {
            var claims = new[]
                    {
                        new Claim("name", "Administrator"),
                        new Claim(ClaimTypes.NameIdentifier, "0001"),
                        new Claim(ClaimTypes.Role, "SiteAdministrator"),
                    };
            var identity = new ClaimsIdentity(claims, "Basic");
            request.User = new ClaimsPrincipal(identity);

        }

        await Next.Invoke(context);
    }
}

Then use the custom authentication middleware in the application startup

app.Use(typeof(LocalAuthenticationMiddleware));

Access the claims via Controller.User API.

var nameClaim = (User as ClaimsPrincipal).Claims.FirstOrDefault(t => t.Type == "name");

References

basic authentication

 authentication  claims

Comments

Related Posts