I’ve spent a lot of time over the last 16 months or so working with ASP.NET Web API and Microsoft.Owin’s UseOAuthAuthorizationServer middleware extending it with custom OAuthAuthorizationServerOptions, ISecureDataFormat<T>, OAuthAuthorizationServerProvider and IAuthenticationTokenProvider implementations.
This included the use of the System.IdentityModel.Tokens InMemorySymmetricSecurityKey used in the SigningCredentials constructor to be used in signing the JWT token. And when I went to port all of this to ASP.NET Core, I learned to my surprise that there is no equivalent to UseOAuthAuthorizationServer middleware and there is no InMemorySymmetricSecurityKey. Instead, you’re on your own for creating your own authentication/authorization middleware and signing a JWT is done using a SymmetricSecurityKey (a class that used to be abstract but now is not).
Here’s my first attempt:
salt = salt ?? "0a987sdf7asdg896asdf6as9df7a7sdf8asd";
var keyBytes = Encoding.UTF8.GetBytes(
Convert.ToBase64String(Encoding.UTF8.GetBytes(SecKey + salt)));
_symmetricSecurityKey = new SymmetricSecurityKey(keyBytes);
_tokenValidationParameters = new TokenValidationParameters
CryptoProviderFactory = _symmetricSecurityKey.CryptoProviderFactory,
ValidateIssuerSigningKey = false, //true,
IssuerSigningKey = _symmetricSecurityKey,
ValidateIssuer = true,
ValidIssuer = "issuername",
ValidateAudience = true,
ValidAudience = "all",
ValidateLifetime = true,
ClockSkew = TimeSpan.Zero
_signingCredentials = new SigningCredentials(_symmetricSecurityKey, "HS256");
A very good blog post on this topic can be found on Stormpath’s blog. I highly recommend you read that blog post. There are any number of ways to code up your “token” endpoint. I like how easy it is to write a custom authentication and authorization token endpoint using ASP.NET Core. More fun with .NET Core to follow.
I really enjoy reading Oren Eini’s blog at https://ayende.com/blog/ and his last two blog posts about a race condition in a TCP interaction he was able to resolve was classic Oren.
Read the first post here. The lesson learned in the second post is don’t switch streams. A very interesting lesson indeed.
If you are not already a fan and reader, I recommend you become one.
I’m a big believer in establishing standards for your REST APIs. I like this one from Microsoft but there are others. What I like about this particular guideline is the structural organization and its brevity. The introductory paragraph provides the reasoning and justification behind REST even when there are language specific SDKs made available.
Developers access most Microsoft Cloud Platform resources via RESTful HTTP interfaces. Although each service typically provides language-specific frameworks to wrap their APIs, all of their operations eventually boil down to REST operations over HTTP. Microsoft must support a wide range of clients and services and cannot rely on rich frameworks being available for every development environment. Thus a goal of these guidelines is to ensure Microsoft REST APIs can be easily and consistently consumed by any client with basic HTTP support.
One thing that would be nice to have is a standard for filtering, paging, etc., on the URL as query parameters. These get defined differently by every REST service architect out there. Or so it seems. A good jumping off point for some research and thought.
And I want to thank my friend Pablo for sending me the link to this.
Yesterday I installed the Visual Studio 2015 Update 3 and began playing with a new ASP.NET Core API project. But the NuGet packages needed to be updated and when I tried to update them, they could not be found.
Clue: Pay attention to the little black flag in the upper right corner of Visual Studio 2015 () and install the .NET Core 1.0.0. VS 2015 Tooling Preview 2.
The install took a fair amount of time, but when it was done, I created a new ASP.NET Core API project and bada-bing, everything seems happy.
This super helpful error message and some Googling led to a solution. I really did not believe it when I found it. But some days are like that.
Severity Code Description Project File Line Suppression State
Error Web deployment task failed. ((6/29/2016 10:07:24 AM) An error occurred when the request was processed on the remote computer.)
(6/29/2016 10:07:24 AM) An error occurred when the request was processed on the remote computer. Unable to perform the operation. Please contact your server administrator to check authorization and delegation settings.
And the winning blog post (certainly not MS docs) goes to A Software Guy’s Blog (Eric Kelm).
When you add Microsoft Web Deploy to an IIS server, the install adds two local user accounts, both with an expiring password. So 90 days, or whatever your expiration policy is, after you install, web deployment just stops working. The trick is to modify both accounts to check “password never expires”.
Thanks, Eric. And thanks, Microsoft. Eric’s post is four years old and this problem still exists. Epic fail.
This post is primarily a place holder and reminder to review Rick Strahl’s post on this topic a few more times.
The change in default serialization does not yet affect me because I was not relying on RC2 for anything serious. However it is critical to note this default behavior for future reference because many of my APIs serialize “as is” so most of my JSON is PascalCase and changing that midstream would bork every client that relies on case sensitivity in the data.
I particularly like Rick’s take on this:
“Personally I prefer to see stuff like this as an easily accessible option, and not something that is rammed down your throat - serialization shouldn't arbitrarily change the naming of properties. While that is often desirable I'm betting there are plenty of scenarios (especially when dealing with .NET to .NET) where you'd much rather have the serialized content reflect the original naming.
“It's especially frustrating in that this doesn't just affect server code where you could easily refactor, but client side code that may already be running. It also makes it harder to port existing code to ASP.NET core and it's not exactly something that's super easy to find if you're searching unless you already know that there serializer settings being sent to JSON.NET somewhere in the framework.”
Well, now the real play begins with .NET Core 1.0 RTM.
I needed to apply an aspect to my ASP.NET Web API 2 services on every controller. The trick was that I needed an IDisposable object to be created before the action method executed and then disposed when the action method completed. It’s easy enough to write an ActionFilterAttribute to do something at the beginning or at the end of a controller’s action method being called. But how to you maintain state between the OnActionExecuting and the OnActionExecuted events? That’s what this little snippet does.
public class DisposableActionFilterAttribute : ActionFilterAttribute
private readonly IDisposableProvider _provider;
_provider = IoC.Instance.Container.Resolve<IDisposableProvider>();
public override void OnActionExecuting(HttpActionContext actionContext)
IDisposable obj = _provider.CreateDisposableObjectMethod() as IDisposable;
actionContext.Request.Properties[Consts.DisposableObjectPropertyKey] = obj;
public override void OnActionExecuted(HttpActionExecutedContext actionExecutedContext)
IDisposable obj = actionExecutedContext.Request.Properties[Consts.DisposableObjectPropertyKey]
if (null != obj) obj.Dispose();
And now you wire it up and presto change-o, you’ve got an IDisposable created before execution and disposed after execution. And here’s the simple wire up for global application of the attribute in the Global.asax.cs code:
public class WebApiApplication : System.Web.HttpApplication
protected void Application_Start()
I do realize there are many examples of the ActionFilterAttribute and this technique, but it’s easier to search my own blog later when I need to remember how to do this. Happy Monday!
I'm liking the Config[Environment](IApplicationBuilder app) method for Startup class convention
And I like the Startup[Environment] class convention mentioned here
But I am not sure which one I like more. Some experimentation is called for.
And more research to do on writing my own middleware.