DISCLAIMER: IF YOUR FARM WEB APP IS SET TO NEGOTIATE(KERBEROS), READ THIS.
If you are like me, you want SharePoint to be the most simple thing ever, however, if you are like me, it never ever happens that way.
Take my current farm, by all standards it is one of the most solidly built farms ever (PLA), however, there are nuances to that I discover everyday.
You think you have it all figured out and then one day you are on the phone with Premier support and they just take you to the wood shed.
Such a thing happened to me, when i couldn’t get InfoPath browser forms to work in the browser when calling _vti_bin/UserProfileService.asmx SOAP service.
NO matter what I tried, or how many blogs I read, I kept getting the dreaded EVENT ID 5566.
I followed this blog which got me very close, but not all the way, because of KERBEROS. Why Microsoft decided to name it after stuff animals is beyond me.
What the blogs don’t tell you is that if you want to use _vti_bin/UserProfileService.asmx SOAP service to get User Profile INFO, AND YOUR WEB APP AUTHENTICATION PROVIDER IS SET TO NEGOTIATE you have to the following EXTRA STEPS:
- Create a new Secure Store ID and set it to GROUP TICKET. GROUP TICKET is the key to this.
- The secure store credentials need to have the ability to READ Active Directory.
- You will need to convert your InfoPath form data connection into UDCX files, in infopath.
- You will need to create a data connection library and make sure you turn on content publishing (just an option).
- You will need to edit the ucdx files just like in above reference blog, EXCEPT, and this is very important, INSTEAD OF NTLM set it to NEGOTIATE (after all this article start out by pointing that the farm is set to negotiate).
- Don’t use web proxy for infopath
- Make sure you check Configure InfoPath Forms Services is set to Allow user form templates to use authentication information contained in data connection files.
This should work. EVENT ID 5566 should go away.
Kerberos crowd, you’re welcome.
Love
Nando
Recent Comments