When it was released about 4 years ago, ACS was great. It lowered the bar of entry to advanced identity scenarios considerably. Whole chapters of our Claims Identity Guide were focused on ACS! However since its release:

  • There hasn't been much innovation much on it.
  • It is hard to find updated documentation.
  • The dashboard has stayed the same for years.
  • Only a very limited number of IdPs are supported.
  • Visual Studio Add STS Reference and other integrated tools are not available anymore. Configuring ACS on existing solutions is not as easy as it was.
  • Yesterday, Yahoo! connections broke. It took a while for it to be resolved.
  • It's roadmap is unclear.

Many customers with apps configured to use ACS have asked us how difficult it is to replace it with Auth0. It turns out it is very, very easy.

Here's how:

1. Signup to Auth0

No credit card, no commitment. Signup here for a free trial.

2. Register your app

Go to Applications and click on NEW. Select WS-Fed (WIF) Web App.

3. Enter your App's URLs

These 2 parameters correspond to the Realm and Return URL params you configured in ACS:

Press SAVE

4. Update your App Web Config

Scroll down on the same page and you will find two web.config sections you can simply paste into your web application. The first one is for .NET 4.5 projects. The second one is for older systems.

You are done!

You can of course run the Add STS Reference wizard if you are on VS 2010 or the other integrated tools. We supply a metadata endpoint you can import into your project.

Rule Groups: Auth0 rules give you outstanding power to do claims transformation. You have the full JavaScript language and many popular Node.js modules at your disposal to do whatever you can think of. From simple mappings to more complex stuff like tracking sign-ups, enriching User Profile and generating new Leads on Salesforce and Multi-factor auth.

Auth0 vs. ACS

Here's a more detailed comparison of Auth0 and ACS: