Recently somebody asked me about doing APIKey verification in .NET 4. Previously in .NET 3.5 we provided the REST Starter Kit which included a fair bit of server side code to enable a collection of RequestInterceptor objects that we showed doing API Key verification. In this post I’ll show you how you can be a ServiceAuthorizationManager in WCF to accomplish the same goal.
For more info
When you create a RESTFul service on the public web you have to protect yourself from people who might abuse your service. After all, once it is available to the public for use by anonymous users if people start abusing the service by invoking it too much or trying to hack into it you need a way to shut off their access to your service.
I recall a few years ago when I was doing ARCast.TV we started seeing a huge spike in download traffic. We wondered if I had suddenly become very popular, but sadly it turned out to be a buggy add on for Windows Media Center that was repeatedly downloading episodes until it filled up the hard drive, then it would delete them and download again until the users ISP would shut off their connection.
In the world of the web the provider has to pay the bandwidth charges for such bugs so needless to say we weren’t very happy about this. We decided to block that particular program but we couldn’t block it by IP address since there were many customers around the world using it. Fortunately they set the User-Agent string so we could filter out their requests.
But what if they didn’t use the User-Agent string? What if they were a malicious program trying to make my bandwidth charges go so high that I would have no alternative but to shut down the feed? This is where an API Key becomes useful.
Most public Web APIs ask you to sign up for their developer program even if it is free to access their service. Once you sign up, they provide you with an API key that you have to pass whenever you call their service. That way if they detect that your app is buggy or malicious they can simply revoke your API key and you won’t be able to access the service anymore.
In this post we will do the simplest things and in later posts we will consider how you can make this even better with Windows Server AppFabric.
In my example, I’m storing some keys in an XML file that I generated using the DataContractSerializer. The details of how I store and read this file are not important here. Most people will probably store keys in a database or distributed cache. As you can see below, I’ve stored the keys in APIKeys.xml
Implementing a ServiceAuthorizationManager is easy. Don’t let the sample code about claims confuse you – you don’t have to use claims in your authorization manager. In my case, I’ve created some simple code that extracts the APIKey from the query string and searches the list of keys to see if there is a match.
The first step is to obtain the APIKey from the QueryString. To do this I’ve created the following method.
1: public string GetAPIKey(OperationContext operationContext)
3: // Get the request message
4: var request = operationContext.RequestContext.RequestMessage;
6: // Get the HTTP Request
7: var requestProp = (HttpRequestMessageProperty)request.Properties[HttpRequestMessageProperty.Name];
9: // Get the query string
10: NameValueCollection queryParams = HttpUtility.ParseQueryString(requestProp.QueryString);
12: // Return the API key (if present, null if not)
13: return queryParams[APIKEY];
Next I created an APIKeys property on the class. The property getter obtains the list of keys from the cache. In my simple example, I’m using the ASP.NET cache but with some very minor code changes I could use AppFabric Caching to get a truly scalable distributed cache. I put them in the cache because I can control the length of time the keys will remain present. If I revoke a key after a few minutes the list of keys will expire from the cache and the key will be revoked. This small compromise prevents me from having to look up the keys in a database every time a request comes to a service.
1: public List<Guid> APIKeys
5: // Get from the cache
6: // Could also use AppFabric cache for scalability
7: var keys = HttpContext.Current.Cache[APIKEYLIST] as List<Guid>;
9: if (keys == null)
10: keys = PopulateAPIKeys();
12: return keys;
Next I implement a method to validate the API Key. For the purposes of the sample I’ve added a global property that allows you to enable/disable API Key Verification from the home page.
1: public bool IsValidAPIKey(OperationContext operationContext)
3: // if verification is disabled, return true
4: if (Global.APIKeyVerification == false)
5: return true;
7: string key = GetAPIKey(operationContext);
9: Guid apiKey;
11: // Convert the string into a Guid and validate it
12: if (Guid.TryParse(key, out apiKey) && APIKeys.Contains(apiKey))
14: return true;
18: // Send back an HTML reply
19: CreateErrorReply(operationContext, key);
20: return false;
Finally I override the CheckAccessCore method. This is the method that WCF will call to see if I want to allow the call or not.
1: protected override bool CheckAccessCore(OperationContext operationContext)
3: return IsValidAPIKey(operationContext);
Our class is implemented but WCF doesn’t know about it yet. We need to modify web.config to indicate that we have a serviceAuthorization behavior we want to add. In .NET 4 we have simplified WCF configuration so you can create a default behavior set that will be applied to services that do not specify any other behavior. I’m going to take advantage of this to make it really simple. Look at line 6 – this is where I added the ServiceAuthorization behavior. Lines 11-15 add new features for WebHttp services in .NET 4 that provide automatic content negotiation and an auto generated help page.
5: <!-- This behavior enables API Key Verification -->
6: <serviceAuthorization serviceAuthorizationManagerType="WCFWebHttp.APIKeyAuthorization, WCFWebHttp" />
14: helpEnabled="true" />
17: <serviceHostingEnvironment aspNetCompatibilityEnabled="true" />
Give it a try, run the project from Visual Studio. When you start it up, API key verification is disabled.
If you plan on exposing a WebHTTP (REST) service on the public web you really should support API Key verification. This will give you the control to block buggy or malicious apps that are abusing your service. This sample application gives you everything you need to get started.
Recently somebody asked me about doing APIKey verification in .NET 4. Previously in .NET 3.5 we
In .NET 3.5, we created the REST Starter Kit as a way to get you up and running with RESTful services
Recently somebody asked me about doing APIKey verification in .NET 4. Previously in .NET 3.5 we provided