16

I am beginning to believe I am a grossly incompetent programmer. After a lot of reading, I still cannot figure out how to cleanly implement an authentication mechanism for a RESTful WCF Service.

I have tried everything:

  1. Following this guide, only to find out that the proposed authentication mechanism is a ugly hack.

  2. Installing the WCF REST Starter Kit, only to find out it is obsolete and has been replaced with another project template.

  3. Install said project template, only to find out it does not provide any authentication mechanism of its own.

  4. Install an IIS module that provides custom authentication functionality at transport level, only to find out the author provides zero documentation. only to find out I need to implement a MembershipProvider. (I want to provide only an UserNamePasswordValidator.)

Is there any sane way to implement an authentication mechanism for a RESTful WCF Service?

isekaijin
  • 19,076
  • 18
  • 85
  • 153
  • 3
    I went through the exact same path. Having similar problems with dealing with resource hierachies and came to the obvious realization that WCF as it is, doesn't fare well in the REST mindset. You can do it, but it feels hacky. I think the WCF team is aware of it and they are trying to address it (http://wcf.codeplex.com/wikipage?title=WCF%20HTTP). Anyway, looking forward to someones answer here, I could use it. We wrote our own HTTP module for it, but not sane IMO so not an answer. – ale May 16 '11 at 18:45

1 Answers1

10

When I was investigating how to implement security for my own WCF RESTful service I spent some time looking at how other popular services like flickr and amazon implement their own security - assuming that they've probably spent far more time thinking about it than I have. Flickr's documentation in particular helped shaped how I formated my signatures and requests.

In the end I chose a HMAC (Hash-based Message Authentication Code) authentication scheme for my services.

I created a custom HMAC ServiceAuthorizationManager that validates the signature of each request as it comes in. Each request contains the following:

  • a user token
  • timestamp
  • nonce
  • signature

Using this information the manager can look up the user's secret from their token and can recreate the signature on the server using the provided information.

My signature consists of an MD5 hash of the following (values are concatenated together in a specific order and hashed so the value can be repeated on the server):

  • apikey
  • userToken
  • secret
  • timestamp
  • nonce

I store the nonce's in a memcache instance for a short period of time in order to quickly check against any replay attacks. After that time skew (about 10 minutes) the timestamp is used to reject any other old requests.

I can post some snippets of my code if it will help. In general I've found that the HMAC authentication is generally the safest way to go and is easily supported on any clients that will be using your service (not just .NET).

efalconer
  • 2,551
  • 1
  • 17
  • 10
  • 1
    Could you please post somewhere some snippets of your code? It would be very helpful. Or send me through e-mail to kral.konf (at) volny.cz. Thanks! – Karel Kral Dec 30 '11 at 16:09
  • Unfortunately I do not have access to that source at this time, but if I get a moment I'll see if I can whip up another copy (I knew I should have just included it when I wrote the original response). – efalconer Feb 28 '13 at 15:39
  • How long more we have to wait for this example :) – Cruiser KID Aug 08 '15 at 10:53