Thursday, March 15, 2012 9:05 AM
We are working on a Federation scenario wich will work as follows:
1 - Sharepoint and .NET WFE with passive federation using ADFS as STS with some external Claim Provider Trusts (SSO also required)
2 - WCF Claim Aware services configured also to use ADFS
3 - Sharepoint and .NET WFE calling WCF's using ActAs
All points are working with the exception that we did not manage to implement Sharepoint Calls to WCF's using the bootstrap token and the ActAs delegation. It seems that the original ADFS SAML token was rebuilt by the Sharepoint STS and so the bootstrap token used is not recognized by ADFS
Question: How can we implement the ActAs model to allow calls from Sharepoint to Claim Aware WCF Services that are configured to trust ADFS ? We dont want to reconfigure those WCF services to trust the Sharepoint STS instead...
Thursday, March 22, 2012 7:24 PMWe have exactly the same scenario, did you find an answer for this?
Friday, May 04, 2012 2:53 PM
We are working on the exact same scenario.
To test this however I am leaving SharePoint out of the picture and instead created a basic web application trusted by ADFS. We are using this web application to fetch a RST with ActAs like this Rst.ActAs = new SecurityTokenElement(Identity.BootstrapToken) to test the secure Service calls however we are getting an error when trying to get the token TrustChannel.Issue(Rst, out rsts)
I was just curious if you could provide the customBinding from your server side and your config or code from the client side as to maybe it would help with my issues. Maybe I could offer more help on SharePoint after I get this working.