Tuesday, November 12, 2013

Visual Studio 2013: Where is the Identity and Access tool?

In Visual Studio 2012, you had the Identity and Access tool which gave you an easy way to configure your WIF configuration and integrate with an existing STS.

After installing Visual Studio 2013, I started looking on the Visual Studio Gallery for a new version of the tool. But no luck, only a VS 2012 version was available Bedroefde emoticon. And it seems that a version for Visual Studio 2013 will never appear.

Vittorio  Bertocci shared the following information:

In VS2013 Microsoft added support for claims-based identity directly into the ASP.NET project creation experience (see http://blogs.technet.com/b/ad/archive/2013/06/26/improved-windows-azure-active-directory-integration-with-asp-net-amp-visual-studio.aspx ), hence there are no plans of porting the Identity and Access tool to VS2013. We are aware of the fact that as of today the feature set of the two approaches are not 100% equivalent. VS2012 and VS2013 work well side by side, if you depend on functionality only available on the Identity & Access tool we recommend you keep both available until functional parity is reached (see below).

Here there are some comments on the main differences:

6 comments:

Anonymous said...
This comment has been removed by a blog administrator.
Anonymous said...

Is there a migration path from ACS to Mobile Services?

Is there a way for me to obtain the same identifiers?

Anonymous said...

I thought that I really, really needed the identity and access tool, because I need to re-configure Web.config for any of multiple hosts for development and testing and production. The main part was the generation of the thumbprint in the issuerNameRegistry section of Web.config. So, I am guessing that with Visual Studio 2013 I can create a dummy project for each host and copy that section of the Web.config to my real project as I need to move it to each host. On another related issue, I am still waiting for SQL Server Reporting Services to catch up to using Visual Studio 2013, so that I can work on my whole solution without switching IDEs for each project. It always seems to be several months behind. Hint to the big gorilla - I have to play with you, but you don't play nice, so, I might switch to a better playmate as soon as my job allows it.

Anonymous said...

This IS the art of simplicity after all. Once again the tools for working with WS-Federation in Visual Studio are 'simply' broken.

Anonymous said...

All very well for ASP but what about WCF?

Shruti Ramalingam said...
This comment has been removed by a blog administrator.