add support for ACS management service

[gscott]

So we can easily provision ACS entries for apps and sites we create in Node.

http://msdn.microsoft.com/en-us/library/windowsazure/hh278947.aspx

#529

[markcowl]

@glennblock please investigate the custoemr's scenario for acs

[gscott]

The customer is a big fan and is avidly following your repo and would be happy to respond.

We are deploying multiple Node apps to Azure, and we're using ACS. We auto-provision apps (web roles), generate Github repos and Azure deployments, and have the developer go from idea to working "hello world" in Azure using our authorized Node stack in about 10 minutes.

But it still requires me to provision the app as an relying party in ACS — since I use ACS to federate with my corporate ADFS infrastructure.

We're node people so we would love to use the azure-sdk-for-node to add the ACS RP entry in our internal provisioning solution.

Seemed logical since ACS is part of Azure, therefore the azure-sdk-for-node would be comprehensive and support as many Azure features as possible, including ACS.

Not a dealbreaker, but I really really would like to see as much Azure functionality as possible exposed in the SDK.

From: markcowl <notifications@github.commailto:notifications@github.com>
Reply-To: WindowsAzure/azure-sdk-for-node <reply@reply.github.commailto:reply@reply.github.com>
Date: Wednesday, January 16, 2013 2:17 PM
To: WindowsAzure/azure-sdk-for-node <azure-sdk-for-node@noreply.github.commailto:azure-sdk-for-node@noreply.github.com>
Cc: Glenn Scott <gscott@caa.commailto:gscott@caa.com>
Subject: Re: [azure-sdk-for-node] add support for ACS management service (#529)

@glennblockhttps://github.com/glennblock please investigate the custoemr's scenario for acs

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/529#issuecomment-12343541.

---

This e-mail and any files transmitted with it are intended solely for the use of the individual or entity to whom they are addressed. If the reader of this e-mail is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any use dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please e-mail us at caasecurity@caa.com or call 424-288-2000.

[andrerod]

Duplicate of #332

[christav]

Closing as part of backlog scrub. If this is still an issue please reopen.

[gscott]

Nope, we just did it ourselves directly to the documented HTTP API.

[gscott]

BTW, 100% of issues I open on azure-sdk-for-node end with a long wait, perhaps a year, and then getting closed as part of a "scrub." Never, ever paying attention to azure-sdk-for-node again.

Peace be with you dudes.