You’re offline. This is a read only version of the page.
Hello All,
Our situation is we are trying to use the XRM SDK (and XRMToolset) against our Dynamics 365 tenant. Our tenant is not federated with ADFS, but rather another 3rd party IdP. This IdP does support WS-Trust, but does not support WS-Trust 1.3.... thus, when the discovery logic executes, it cannot find the username endpoint of the WS-Trust service, and we think it is because it is looking in the wrong namespace.
According to the documentation from Microsoft on this, there is an ability to set the IssuerEndpoint.TrustVersion to WS-Trust 2005. That reference is here:
https://msdn.microsoft.com/en-us/library/microsoft.xrm.sdk.client.issuerendpoint.trustversion.aspx
We can't find a way to get the SDK samples to change to allow connecting to a WS-Trust endpoint from the following namespace: http://schemas.xmlsoap.org/ws/2005/02/trust
When we watch the connection attempts in Fiddler traces, we see that the code is indeed sweeping through the metadata endpoints and we see clearly that the WS-Trust endpoint is supplied by Microsoft in the GetUserRealm.srf call where we see the following value in the XML: STSAuthURL = https://{our IDP}/WSTrust/Service.svc/trust/username
But again, the code dies saying it can't find the correct username endpoint.
So, my question is, can this even work with the 2005 version or does it require the 1.3 version of WS-Trust? And if so... why the ability to set the trust version... and if we can set the trust version so that the discovery finds the correct endpoint, how can we do that?
Should we be explicitly setting the endpoint URL so that the discovery doesn't have to search the mex for it? Again, we are not using ADFS.
Thanks!
*This post is locked for comments
I have the same question (0)
Share
Report
All responses (
Answers (
4
