endpoint.tv - How to Do API Key Verification with a WCF WebHttp (REST) Service

Posted: Jun 17, 2010 at 7:00 AM

By: Ron Jacobs

23,532 Views

4 Comments

Video format

Option selected may change based on video formats available and browser capability.

Auto

Use our suggested format for this video.

Smooth Streaming

Adaptive bitrate streaming - little buffering but lower video quality at times of low bandwidth. Silverlight 5 required

Progressive

Traditional buffered video format. Silverlight 5 required

HTML5

For browsers that support H.264 MP4 or WebM video playback such as:
IE9+, Firefox 4+, Chrome 5+, or Safari 4+.

Flash

For browsers that have the Adobe Flash Player plugin installed.

Follow the Discussion

Oops, something didn't work.

Try again?

Getting "follow" information

Stop following these comments

Start following these comments

Removing your "follow"

Setting up your "follow"

Subscribe to this comments

@Steve Scott: Thanks for your fine solution. I have changed it little so it can also be used with (OData) Service references. I also check the header of the request:
public string GetAPIKey(OperationContext operationContext)
{
var request = operationContext.RequestContext.RequestMessage;
   var requestProp =
      (HttpRequestMessageProperty)request.
            Properties[HttpRequestMessageProperty.Name];
   NameValueCollection queryParams =
      HttpUtility.ParseQueryString(requestProp.QueryString);
string apiKey = queryParams[APIKEY];
if (apiKey == null)
{
    apiKey = requestProp.Headers[APIKEY];
}
return apiKey;
}
and on the client, i pass the ApiKey in the header using the SendingRequest event:
service.SendingRequest += new
EventHandler<System.Data.Services.Client.SendingRequestEventArgs>
    (service_SendingRequest);

static void service_SendingRequest(object sender,
System.Data.Services.Client.SendingRequestEventArgs e)
{
   e.Request.Headers.Add("APIkey", "918704ec-4811-45b6-a169-16bae3df69a8");
}
See also:
http://adi.atosoriginblog.nl/2010/12/28/flexibel-apikey-gebruik-bij-wcf-data-services/

Follow
Oops, something didn't work.

Try again?

Sign In to be begin to follow these comments

What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in. You need to be signed in to Channel 9 to use this feature.

Getting "follow" information

Stop following these comments

Start following these comments

What does this mean?
Following an item on Channel 9 allows you to watch for new content and comments that you are interested in and view them all on your notifications page.

Removing your "follow"

Setting up your "follow"

Did you know you can
sign up for email notifications?
- Subscribe to this comments

scyonx

Jun 18, 2010 at 6:57 AM

Is there going to be a REST Starter Kit version for .NET 4??
rojacobs Ron Jacobs

Jun 18, 2010 at 6:11 PM

Still working on the plan. Most of the server stuff ended up in .NET 4. The only part that we don't have is the HttpClient library (which is really cool). It totally works on .NET 4 if you just grab the source and build it.
Steve Scott

Jul 03, 2010 at 8:52 PM

How do we pass it in if we're using the WebReference ServiceClient object?
Sander van de Velde

Dec 28, 2010 at 7:21 AM

@Steve Scott: Thanks for your fine solution. I have changed it little so it can also be used with (OData) Service references. I also check the header of the request:
public string GetAPIKey(OperationContext operationContext)
{
var request = operationContext.RequestContext.RequestMessage;
   var requestProp =
      (HttpRequestMessageProperty)request.
            Properties[HttpRequestMessageProperty.Name];
   NameValueCollection queryParams =
      HttpUtility.ParseQueryString(requestProp.QueryString);
string apiKey = queryParams[APIKEY];
if (apiKey == null)
{
    apiKey = requestProp.Headers[APIKEY];
}
return apiKey;
}
and on the client, i pass the ApiKey in the header using the SendingRequest event:
service.SendingRequest += new
EventHandler<System.Data.Services.Client.SendingRequestEventArgs>
    (service_SendingRequest);

static void service_SendingRequest(object sender,
System.Data.Services.Client.SendingRequestEventArgs e)
{
   e.Request.Headers.Add("APIkey", "918704ec-4811-45b6-a169-16bae3df69a8");
}
See also:
http://adi.atosoriginblog.nl/2010/12/28/flexibel-apikey-gebruik-bij-wcf-data-services/

Remove this comment

Remove this thread

Comments Closed

Comments have been closed since this content was published more than 30 days ago, but if you'd like to continue the conversation, please create a new thread in our Forums,
or Contact Us and let us know.