This is my problem: I created a blank VS12 solution and added one ASP.NET MVC 4 web application, click F5, everything works perfectly. Then, I configured the project to use local development STS through the shiny new wizard (all default options), click F5 and… when I was redirected to it STS cannot respond at the time.
Preliminary request:
GET http://localhost:4826/ HTTP/1.1
From Web Application response:
HTTP/1.1 302 Found
Location: http://localhost:12230/wsFederationSTS/Issue?wa=wsignin1.0&wtrealm=http% 3a%2f%2flocalhost%3a4826%2f&wctx=rm%3d0%26id%3dpassive%26ru%3d%252f&wct=2013-01-05T04%3a56%3a13Z
How to troubleshoot unresponsive STS? I don’t even know where it runs. (This is one of the several benefits of having your own STS project before WIF 4.5.:))
Edit (9:45 AM on January 5): I tried to run the web application in IIS instead of IIS Express-but no success. I also uninstalled and reinstalled the identity and access tools with no luck.
All the screenshots I saw online Both show the notification icon of the LocalSTS service when you start debugging; I haven’t seen this appear yet.
I also compared the .csproj files before and after adding the STS configuration; I didn’t see any changes , Did not even add the project type GUID. This makes me wonder what went wrong; if nothing is specified in the project file, how does the WIF tool know to start LocalSTS? Any ideas? How should this mechanism work?
Edit (January 5th, 10:33 AM): I installed the Claims Aware MVC Application sample and ran it, and LocalSTS started immediately. But after comparing the project files (.csproj, Web.config) Etc.) After that, I found that there is no meaningful difference to mark the WIF tool as a project instead of another project to start LocalSTS. At least now I know the tool is installed correctly. Any ideas on where I should look?
According to scientific experiments, if the project is located under the root node of the solution, that is, not under the solution folder, the Identity and Access Tool will only start LocalSTS for the MVC4 project configured by WIF.
< p>I think I’m going to report a bug… but I’m glad it’s available now.
I recently re-saved my with Windows 8 Pro x64 and Visual Studio 2012 Ultimate Machine. This usually makes me very happy :), except that I encountered some obstacles during the development process due to missing dependencies or Windows components. This is the identity and access tool (as far as I know).
This is my problem: I created a blank VS12 solution, added an ASP.NET MVC 4 Web application, clicked F5, everything worked perfectly. Then, I configured the project to use the local development STS pass Shiny new wizard (all default options), click F5 and… STS cannot respond when I am redirected to it.
Preliminary requirements:
GET http://localhost:4826/ HTTP/1.1
Response from the web application:
HTTP/1.1 302 Found
Location: http://localhost:12230/wsFederationSTS/Issue?wa=wsignin1.0&wtrealm=http%3a%2f%2flocalhost%3a4826%2f&wctx=rm%3d0%26id%3dpassive%26ru%3d%252f&wct=2013-01- 05T04%3a56%3a13Z
How to troubleshoot unresponsive STS? I don’t even know where it runs. (This is one of the several benefits of having your own STS project before WIF 4.5.:))
Edit (9:45 AM on January 5): I tried to run the web application in IIS instead of IIS Express-but no success. I also uninstalled and reinstalled the identity and access tools with no luck.
All the screenshots I saw online Both show the notification icon of the LocalSTS service when you start debugging; I haven’t seen this appear yet.
I also compared the .csproj files before and after adding the STS configuration; I didn’t see any changes , Did not even add the project type GUID. This makes me wonder what went wrong; if nothing is specified in the project file, how does the WIF tool know to start LocalSTS? Any ideas? How should this mechanism work?
Edit (January 5th, 10:33 am): I installed the Claims Aware MVC Application sample and ran it, and LocalSTS started immediately. But after comparing the project files (.csproj, Web.config) Etc.) After that, I found that there is no meaningful difference to mark the WIF tool as a project instead of another project to start LocalSTS. At least now I know the tool is installed correctly. Any ideas on where I should look?
I can’t believe it, it’s too painful, it’s fun.
It turns out that, according to scientific experiments, If the project is located under the root node of the solution, that is, not under the solution folder, Identity and Access Tool will only start LocalSTS for MVC4 projects configured by WIF.
I think I’m going to report an error… but it’s very Glad to be available now.