Data Connections

Re: Issues using certain Data Connections with SharePoint 2013 Claims Based authentication

Rudy007 — Sat, 05 Mar 2016 13:17:28 GMT

Hello All, We had configured a Form based Authentication in sharepoint 2010, where we have 2 list. The form of second list is modified by infopath & by dataconnections we are fetching choice from first list as a lookup. here by windows authentication form is running perfectly fine but when we are opening the same form with FBA. the choice fields were not get displayed ! as suggested above we dome the below changes in web.config file but unable to found in web.config file. after all the above we reset the iis but still no changes. can someone help here ! please mail me at rudreshtewari@gmail.com

Re: Issues using certain Data Connections with SharePoint 2013 Claims Based authentication

donstephen — Tue, 18 Aug 2015 14:31:35 GMT

This is very good information. Thanks for posting it.

Re: Issues using certain Data Connections with SharePoint 2013 Claims Based authentication

howitzer1972 — Tue, 18 Aug 2015 13:14:34 GMT

Hi Don,

Thanks for the suggestion, I actually was already using UDCX and using Secure Store Service credentials in the Authentication node.

After a lot of troubleshooting I was finally able to get this to work. I don't know why this was so difficult to get working in 2013. The Claims based sites in 2010 worked with no problem and exactly as I expected them to; by configuring the Secure Store Service with a Target Application that has credentials to the site I'm pulling data from.

I found 2 workarounds that allowed the data connections to refresh without error:

1. Disable Anonymous Authentication and remove Authentication from the udcx connection file.

Modify the web.config for your web application. Change the AllowAnonymousImpersonation key from true to false.

Make sure that the udcx data connection has the <udc:Authentication> node commented out.

When you make this change the IIS logs show that the Query requests are executed under the web application service account and everything works.

2. Instead of changing the AllowAnonymousImpersonation setting, set the Credentials for the Secure Store Service Target Application to the same account used for the Web Application Service.
Make sure the udcx is using this Group/Group Ticket Target Application in the <udc:Authentication> node.

This allowed the query to work, checking the IIS logs shows that all queries to owssvr are sent under the Service Account for the web application instead of the account I had configured for accessing the data. No idea why I can't use other accounts to query the data in InfoPath. I tried this on 3 different 2013 environments, 2 on my corporate domain and one on a isolated 2013 environment and I had the same issue on all.

The following links helped me in resolving the issue:

http://www.cleverworkarounds.com/2013/10/

http://surviving-sharepoint.blogspot.ca/2013/10/sharepoint-2013-access-denied-using-web.html

Re: Issues using certain Data Connections with SharePoint 2013 Claims Based authentication

donstephen — Fri, 31 Jul 2015 14:10:39 GMT

Hi howitzer1972,

We have been seeing a some bugs using REST Data Connections on a SharePoint 2013 environment. I would suggest converting the REST and owssvr.dll data connections to UDCX. If it still doesn't work, you may need to modify and add credentials to the UDCX. I hope I am able to point you toward the right direction.

Regards,

Issues using certain Data Connections with SharePoint 2013 Claims Based authentication

howitzer1972 — Thu, 23 Jul 2015 19:09:32 GMT

I'm evaluating moving our SP2010 environment to SP2013. One major issue I've found is when using XML Data Connections using owssvr.dll or REST Data Connections using ListData.svc, I get Access errors when querying the data connection via a rule. When the form initially loads, everything works fine and the data from those connections loads into the repeating tables. When trying to change the parameters and re-query it always fails with an Access Denied error. I have no issues using the GetUserProfileByName or GetUserCollectionFromGroup web services. Setting up the Secure Store Service and adding the lines allowed those web services to work fine. I built a 2013 dev environment (off of my domain) to test and it's the same error. I also created Claims based application on my 2010 Prod and UAT environment and they work fine, no issues at all. Is this error just related to SP 2013? I've spent more time trying investigating and troubleshooting this issue than any other problem I've had with SharePoint; I just don't know what else to try. I've gone through MSDN/Technet/MS Forums and can't find anything from Microsoft that says it doesn't work. I hope someone can provide a definitive answer regarding this issue. Thanks