SharePoint 2013: Adding NT Authority\Anonymous Logon to Business Data Connectivity
Have you ever heard the phrase 'There is method in madness'?, I'm sure you have. Have you experienced it? I did recently when attempting to give 'NT AUTHORITY\ANONYMOUS LOGON' access to the Set Object Permission to a Business Data Connectivity (BDC) service on SharePoint 2013 Central Administration.
Description:
A recent task required me to give 'NT AUTHORITY\ANONYMOUS LOGON' access to a BDC service on our SharePoint 2013 environment. At first I wasn't able to do so. We have a SharePoint 2013, three tier environment setup on Windows 2012 servers and SQL 2012. Our servers have been patched up to the August 2013 CU
How and where I experienced the error:
Adding users to BDC's connections is simple.
1. You go to your Central Administration.
- Under Service Applications, click on Manage Service Application:
https://98pwsq.dm1.livefilestore.com/y2py8HYRxpGhxCpF0V4Kilt5wYamogOOXp3J0eS3vihzKiS2Fl-EIpIBSSQ2GPEUXi308Bu7bqkOcgPQLemqJT-MLKumhJj3iKqLQXvFoLGU2A/Capture1.PNG?psid=1
3. Go to your Business Data Connectivity Service Application. Select a Connectivity and click on Set Object Permissions.
https://pspwsq.dm2302.livefilestore.com/y2pjlNPoviEU-7ksu_x3SAtN9uBzUXsI3xlJvLoQyjRfd1B-5wnZvTdlvqtkmtrob-2j0WWTO9ycp6-L6mjwhgyU2kiASxYfClidg4gGGxAxms/Capture2.PNG?psid=1
https://98pwsq.dm2302.livefilestore.com/y2pGc2XVEbdxeRyvy0xQB-VuaEqWuhW-qZUkqIsri5o60hKDouPKYkb6aAY6mVrFl5jzPVajZ6zLcy-GKwsAb2CHLeFhf-RJsAPA0i5Br4yVFI/Capture3.PNG?psid=1
4. Type in 'NT Authority\Anonymous Logon' and hit Enter. The account is confirmed as shown below.
https://98pwsq.dm2301.livefilestore.com/y2pptZwUTA-X51C-Hk2v-NWNTMm9X7tX97z610L6heE53K8FBf9MoZ_3U0DhNUy9RRt_64DhjfuprYrDqXfganB_rrT0VLM2YveMw26e_lv7Ek/Capture4.PNG?psid=1
https://98pwsq.dm2301.livefilestore.com/y2pnltgHQavKlbs7w6CjfsiYI_DKsMOZzoD_leFec2xXGdRUXM0LRCLswhAPK8UDPmVzhfRd7SCIQ2O2jVjXqUJJscVZunf2uZ3akFRLSiUQuw/Capture4a.PNG?psid=1
5. Now hit Enter or click Add. Below is what you will most probably get.
https://98pwsq.dm2303.livefilestore.com/y2pfdsoe9ux0OaLGsbf_PPoFAX-Qp7qsA2XX-tqxNZWZNVN4iXN6vy84P01tv-CzidESqWTKGDnQWoDatPYABJjaMEp4IF4ZyBWuxg6ox7Ft04/Capture5.PNG?psid=1
Things I tried that didn't work:
So when we run into an issue what do we do? 'We Bing or Google' since this is a Microsoft related issue, I Binged more than Googled.
At first I came across several articles which spoke about everything and anything you need for BCS except the one I need. Finally, I stumbled upon the below article:
http://www.dontpapanic.com/blog/?p=131
In this article, the author Paul Papanek talks about editing BDC Model's XML file to make add the Anonymous logon account. I must point out that this article was written for SharePoint 2010 and the steps didn't work for me in SharePoint 2013.
Accidental discovery that worked:
Below are the steps I tried which worked for me. I am not kidding when I state that this was an accidental discovery. Here is what I did-
- I went back to the same BDC service application mentioned above and typed in the name NT Authority\Anonymous Logon.
- I didn't hit the enter button, but instead clicked the Add button TWICE in quick succession.
Clicking the Add button twice confirmed that the NT Authority\Anonymous Logon is a legitimate account and will also add it without any errors.
https://98pwsq.dm2304.livefilestore.com/y2ppWrFOaIGEFpA2GQ8pyKVfetAOAt3QxsvT53lMgzyR1CHlOH5MacnwLuxW0YF8rTfjMOQfecJ7MOyUn2u_orotyxVGBNuDKM1c2iwLDGOF8E/Capture6.PNG?psid=1
Video demo:
Below is a short video of me demonstrating the error and the click twice approach. In the video, I have already selected a random BDC and am attempting to add the NT Authority\Anonymous Logon account. I purposely increased the microphone volume so that you can hear hit the Enter button and/or click on the mouse key. In the video I tried three different times to add the NT Authority\Anonymous Logon account.
- Simply type the account name and hit enter,
- Type the account name and hit enter twice,
- Type the account name and hit the Add button twice in quick succession.
Conclusion:
I'm quite sure that this isn't the only way to resolve this issue, however, it worked for me and perhaps it might work for someone else as well.