Detecting language please wait for.......
I have created a DotNet based Program (Developed using C# and Visual Studio) that
However, our deployment stack is all Docker + Linux, and I was wondering if anyone had any luck connecting to Tridion from a DotNetCore application.
I am getting the following errors when porting the program over to DotNetCore:
Error when Importing a web reference
Resolving project references ...
Importing web service metadata ...
Number of service endpoints found: 2
Scaffolding service reference code ...
Warning:Warning: Cannot import wsdl:port
XPath to Error Source: //wsdl:definitions[@targetNamespace='http://tempuri.org/']/wsdl:service[@name='Application']/wsdl:port[@name='CustomBinding_Application']
Warning:Warning: No endpoints compatible with .Net Core apps were found.
XPath to Error Source: //wsdl:definitions[@targetNamespace='http://tempuri.org/']/wsdl:service[@name='Application']/wsdl:port[@name='CustomBinding_Application1']
Warning:Warning: Cannot import wsdl:binding
Detail: An exception was thrown in a call to a policy import extension.
Error: An exception was thrown in a call to a policy import extension.
Error: The method or operation is not implemented.
XPath to Error Source: //wsdl:definitions[@targetNamespace='http://tempuri.org/']/wsdl:binding[@name='CustomBinding_Application']
XPath to Error Source: //wsdl:definitions[@targetNamespace='http://tempuri.org/']/wsdl:binding[@name='CustomBinding_Application1']
Updating project ...
Last time I investigated - admittedly around .NET Core 2.1 - I couldn't get it working either for ISHRemote. ISHRemote is a C# PowerShell library on top of the WCF WS-Trust-authenticated SOAP API of Tridion Docs. It is currently also blocking me to make ISHRemote PowerShell v6/7 (which are .NET Core based) ready. See also https://github.com/sdl/ISHRemote/issues/81
So if you have more insights on the current state of affairs, please share.
Would support for message level security in dotnetcore help you get unblocked? I ended up in the following github issues after googling the issues I was having. I am assuming that Ws-Trust is based in message security. Dotnet core 3 seems to have a solution for it.
https://github.com/dotnet/wcf/pull/3657 is the merged PR
https://github.com/dotnet/wcf/issues/3 is the issue that was raised - it says at the end of the message that this is resolved.
I was using dotnet core 3.1 and some of the imports required didn't work for me. Potentially because of lack of my understanding of ws-trust. <shrug>.
To support WS-Federation/WS-Trust you have to have more than message security... According to portability scanner we are missing the following libraries/types in dotnetcore
Probably because those libraries use the underlying (Windows) OS regarding certificates and more. And that makes them not easy to port cross-platform. As said I'm keeping an eye on it, but for now we are blocked.