Skip to content
This repository has been archived by the owner on Dec 14, 2017. It is now read-only.

WsFederationController conflict with IdentityServer3 Admin #88

Open
pwil301 opened this issue Jul 21, 2017 · 0 comments
Open

WsFederationController conflict with IdentityServer3 Admin #88

pwil301 opened this issue Jul 21, 2017 · 0 comments

Comments

@pwil301
Copy link

pwil301 commented Jul 21, 2017

Using the host samples provided in the repos for guidance, I set up IdentityServer3 (build 2.6.0.0) Core, EntityFramework, WsFederation, WsFederation EntityFramework, and Admin, Admin EntityFramework. Items mapped under "/core" (IdSrv and Wsfed) work fine. However, when attempting to access "/adm" to get to the admin component, I receive the following exception content:

{"message":"An error has occurred.","exceptionMessage":"An error occurred when trying to create a controller of type 'WsFederationController'. Make sure that the controller has a parameterless public constructor.","exceptionType":"System.InvalidOperationException","stackTrace":" at System.Web.Http.Dispatcher.DefaultHttpControllerActivator.Create(HttpRequestMessage request, HttpControllerDescriptor controllerDescriptor, Type controllerType)\r\n at System.Web.Http.Controllers.HttpControllerDescriptor.CreateController(HttpRequestMessage request)\r\n at System.Web.Http.Dispatcher.HttpControllerDispatcher.d__1.MoveNext()","innerException":{"message":"An error has occurred.","exceptionMessage":"Type 'IdentityServer3.WsFederation.WsFederationController' does not have a default constructor","exceptionType":"System.ArgumentException","stackTrace":" at System.Linq.Expressions.Expression.New(Type type)\r\n at System.Web.Http.Internal.TypeActivator.Create[TBase](Type instanceType)\r\n at System.Web.Http.Dispatcher.DefaultHttpControllerActivator.GetInstanceOrActivator(HttpRequestMessage request, Type controllerType, Func`1& activator)\r\n at System.Web.Http.Dispatcher.DefaultHttpControllerActivator.Create(HttpRequestMessage request, HttpControllerDescriptor controllerDescriptor, Type controllerType)"}}

The admin section worked prior to adding the WsFederationPlugin to the project. Now, however, even if I comment out the ConfigurePlugins method that wires up WsFed, it still results in the same error. Is there a default path being mapped somewhere in the WsFed project that would override anything not under my root path, "/core"?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant