Hmm, i dont see any replacement of controller resolver service in webapi, wont it pickup any controller referenced by the app? https://github.com/thinktecture/Thinktecture.IdentityServer.v3/blob/5a6dd546ad437fd1e0213b68f617907f43b3a4c2/source/Core/Configuration/Hosting/WebApiConfig.cs
feel free to double-check and then let me know :)
is there a newer nuget?
nvm
i used the <,> generic version
form the IDependencyResolver, can i resolve a owin context for the request?
is it also this resolver that is passed to me in the registration ?
@brockallen I want it because we have our own DI on the context that I would like to resolve the usermanager and rolemanager from to pass to idm like i did with idsrv here: https://gist.github.com/s093294/f6c39fcbb1207b760c90
i don't understand the comment about the DI being incomplete?
it's just copied from idsvr
unless i missed something
it would be usefull for me with the environment, but if its not there i will find a different path
on myget
btw i saw you used a PropertyValue, do you know if webapi can deserialize to that from a plain form urlencoded post, or do you fix it on client before posting?
feature request or idea. Would be nice if identity manager did something similar to idsrv when getting claims. Such the phone,email would show as claims. Or alternative on the properties tab, allow the userservice to register additional properties to show in the properties tab
the property concept is an abstract thing
and there's a get/set pair for you to do whatever you want
you just need to do this in the metadata
making it easier to build custom metadata is a pain now, tho
so that needs improvement
or would i need to do a PR with it to get it in
it might be in the MR or AspId sample hosts... or even in the core in-mem host
any reason why you left out the email verified and phone verified and username in default implementation
or naa that was deault true