I’ve just read this page: http://msdn.microsoft.com/en-us/library/dd320275.aspx.
I wonder if you should use the shared key *lite* scheme instead:

ChallengeResponse challengeResponse = new ChallengeResponse(
ChallengeScheme.HTTP_MS_SHAREDKEY_LITE,
“…″,
“…”);

best regards,
Thierry Boileau

That sounds surprising because there should be not difference between a remote service and a local one.
Would be so kind as to share your issue by posting to our “discuss” list?
http://www.restlet.org/community/lists

best regards,
Thierry Boileau

Interestingly, this works fine against the cloud service, but wont seem to work against the development storage that you can run locally.

Client client = new Client(Protocol.HTTP);
ChallengeResponse challengeResponse = new ChallengeResponse(
ChallengeScheme.HTTP_MS_SHAREDKEY,
“devstoreaccount1″,
“Eby8vdM02xNOcqFlqUwJPLlmEtlCDXJ1OUzFT50uSRZ6IFsuFq2UVErCz4I6tq/K1SZFPTOtr/KBHBeksoGMGw==”);
Request request = new Request(Method.DELETE,
“http://127.0.0.1:10001/testQueue”);
request.setChallengeResponse(challengeResponse);
Response response = client.handle(request);
System.out.println(response.getStatus());

Comes back with

Forbidden (403) – Server failed to authenticate the request. Make sure the value of Authorization header is formed correctly including the signature.

Is this a bug? Is there a mailing list where I should be posting this to instead?

Thanks!

here is a sample client code that delete a queue called “testQueue”:

Client client = new Client(Protocol.HTTP);
ChallengeResponse challengeResponse =
new ChallengeResponse(
ChallengeScheme.HTTP_MS_SHAREDKEY,
“[account]“,
“[password]“);
Request request = new Request(Method.DELETE,
“http://[account].queue.core.windows.net/testQueue”);
request.setChallengeResponse(challengeResponse);
Response response = client.handle(request);
System.out.println(response.getStatus());

I hope that helps you.
Best regards,
Thierry Boileau