Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Azure ACS offers OAuth and OpenID providers, and now that ASP.NET 4.5 offers the same thing, without the added cost, is there any reason for a .NET developer to consider ACS?

(Disclaimer, I don't know what version of oauth each service provides)

share|improve this question

closed as primarily opinion-based by Snowman, durron597, MichaelT, gnat, Ixrec Oct 3 '15 at 19:45

Many good questions generate some degree of opinion based on expert experience, but answers to this question will tend to be almost entirely based on opinions, rather than facts, references, or specific expertise.If this question can be reworded to fit the rules in the help center, please edit the question.

up vote 5 down vote accepted

The primary benefit to using ACS is that you can integrate login systems which are not compatible with DotNetOpenAuth; namely, that you could combine external logins with an Active Directory (including both on-premises AD as well as AD in the cloud like Office 365). Your customers could use their accustomed identities from 3rd parties, and your administrative team could use their existing domain credentials.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.