<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.infopathdev.com:443/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>SharePoint Integration</title><link>https://www.infopathdev.com:443/forums/46.aspx</link><description> For questions concerning issues in the integration of SharePoint and Microsoft InfoPath.</description><dc:language>en</dc:language><generator>CommunityServer 2007 SP3 (Build: 31118.962)</generator><item><title>Kerberos authentication delegation...</title><link>https://www.infopathdev.com:443/forums/thread/25389.aspx</link><pubDate>Thu, 03 Jan 2008 18:03:32 GMT</pubDate><guid isPermaLink="false">033a2e2d-04e2-4a9d-be01-a4634161eefd:25389</guid><dc:creator>Karsten Brocksieper</dc:creator><slash:comments>0</slash:comments><comments>https://www.infopathdev.com:443/forums/thread/25389.aspx</comments><wfw:commentRss>https://www.infopathdev.com:443/forums/commentrss.aspx?SectionID=46&amp;PostID=25389</wfw:commentRss><description>&lt;p&gt;Hi all,&lt;/p&gt;
&lt;p align="left"&gt;I&amp;#39;m facing an authentication delegation issue in MOSS 2007. The setup and problem is described below. If you need any more details feel free to ask.&lt;/p&gt;
&lt;p&gt;Basically the setup I&amp;#39;m looking at is the following:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;MOSS2007 enterprise server = SRV1 
&lt;li&gt;Member server with SQL Server 2005&amp;nbsp;= SRV2 
&lt;li&gt;Member server with IIS and ASP.NET = SRV3 
&lt;li&gt;Client = CLIENT &lt;img alt="Big Smile" src="http://forums.microsoft.com/MSDN/emoticons/emotion-2.gif" /&gt;&lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;All systems and service accounts have been properly configured so that the required SPN&amp;#39;s are there and Kerberos constrained delegation is enabled. Furthermore all IIS servers and Sharepoint have been configured to support integrated authentication. I have verified that authentication is in fact taking place through Kerberos, just to make sure NTLM is not in the way.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve installed a webservice on SRV3 which connects to a DB on SRV2 using integrated authentication. All it does it read&amp;nbsp;different columns from the DB. It is setup properly to impersonate the user who accesses the webservice. When testing the webservice directly&amp;nbsp;from&amp;nbsp;the client&amp;nbsp;everything works fine and I get the expected results back.&lt;/p&gt;
&lt;p&gt;So we move on and create a basic form in infopath which uses the webservice to fill different text boxes. When I test this form in infopath fat client everything works fine, without asking for authentication so integrated auth works. Now when I publish this form to a sharepoint library and try to open it from CLIENT it does &lt;strong&gt;not&lt;/strong&gt; work and provide me with the well known error &amp;quot;&lt;em&gt;An error occurred accessing a data source&lt;/em&gt;&amp;quot;.&lt;/p&gt;
&lt;p&gt;When I check in the sharepoint logs I get the following:&lt;/p&gt;
&lt;p&gt;System.Net.WebException: The remote server returned an error: (401) Unauthorized. ...&lt;/p&gt;
&lt;p&gt;When I check the entries in the IIS log on SRV3 I can see the 401, and it does not provide any user authentication. Also when I use a network sniffer to check kerberos traffic I can clearly see that Sharepoint isn&amp;#39;t even trying to get a kerberos ticket for the user and the service HTTP/SRV3.&lt;/p&gt;
&lt;p&gt;I&amp;#39;ve also checked out some other possibilities, such as MOSS sso, but to no avail. At this point I can only come to the conclusion that sharepoint does not attempt to authenticate to the back-end webservice with the users credentials.&lt;/p&gt;
&lt;p&gt;So does anyone have a clue as to what the reason for this issue might be? Does anyone have a clue?&lt;/p&gt;
&lt;p&gt;I can get everything to work just fine when I define a static user in the webservice to connect to the DB and allow anonymous access to the webservice. However this is&amp;nbsp;not a good base to build an enterprise solution on. Auditing should be available at all levels of the information chain, certainly on the DB level.&lt;/p&gt;
&lt;p&gt;Any help would be appreciated,&lt;/p&gt;
&lt;p&gt;Regards&lt;/p&gt;</description></item></channel></rss>