There is a problem there, the DOTNET_BS endpoint has been changed to support claim based security (it expects a SAML token with the user claims). Therefore, the DOTNET_CLIENT client is negotiating a SAML token before calling that service. I don't think the WSAS_BS endpoint is expecting that.
-----Original Message----- From: Chintana Wilamuna [mailto:[email protected]] Sent: Wednesday, October 14, 2009 6:19 AM To: [email protected] Subject: Re: .Net new passive STS impl. On Tue, Oct 13, 2009 at 11:06 PM, Chintana Wilamuna <[email protected]> wrote: > On Tue, Oct 13, 2009 at 10:50 PM, Pablo Cibraro > <[email protected]> wrote: > >> "System.Reflection.AmbiguousMatchException: Ambiguous match found. ". It >> looks like an issue with the binaries, could you please, cleanup all the >> binary folders and rebuild everything from scratch ?. If the problem still >> exists after that, let me know. > > I tried with BuildDotNet.cmd and also tried opening up each .sln, > build everything after cleaning. In both instances, I'm seeing the > same exception. This situation only occurs when the setup is DOTNET_CLIENT -> WSAS_BS. For DOTNET_CLIENT -> DOTNET_BS it doesn't give this error and everything work as expected. Wonder whether I have to do any extra step after changing to the WSAS_BS. Bye, -Chintana -- http://engwar.com/
