Article ID: 2643420 - Last Review: December 14, 2011 - Revision: 5.0

SharePoint 2010: Organization Browser web part does not render for Windows Claims users

View products that this article applies to.

System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.

SYMPTOMS

When using the Organization Browser Web Part on Windows Claims enabled sites, the web part does not render any information. The same web part renders users with different Claims Authentication types correctly.

Back to the top

CAUSE

The organization information is pulled from the profile database of the User Profile Service Application (UPSA). The required information is stored in the UserProfile_Full table.

Active Directory users (either added manually or synchronized automatically) are stored in the UPSA Profile Database with NETBIOS\LogonName (Ex.: CONTOSO\TestUser1) format.

When browsing a claims site however, the user context uses the Claims NTName format. (Ex.: i:0#.w|Contoso\TestUser1)

The Organization Browser web part then does a database lookup for the user 'i'0#.w|Contoso\TestUser1' which is not available in the database since the user information will be stored with the 'CONTOSO\TestUser1' NTName.

The issue does not happen with any other Claims Authentication type as the Profile Database contains the correct naming format for them.

Back to the top

RESOLUTION

The Organization Browser Web Part control is rendered on the page by the CreateHierarchyChartControl javascript function. This function is not aware of the fact that the UPSA Profile Database stores the Windows Claims users with a different naming format. To work around this, the below code snippet must be entered in to the site source right after the Organization Browser web part.

<script type="text/javascript">
 function CreateHierarchyChartControl(parentId, profileId, type, persistControlId) {
  var i = profileId.indexOf("|");
  var claimsmode = profileId.substr(i-1,1);
  if((i >=0 ) & (claimsmode=="w"))
  {
   profileId = profileId.substr(i+1,profileId.length-i-1);
   var initParam = profileId + ',' + type + ',' + persistControlId;
   var host = document.getElementById(parentId);
   host.setAttribute('width', '100%');
   host.setAttribute('height', '100%');
   Silverlight.createObject('/_layouts/ClientBin/hierarchychart.xap',
    host,
    'ProfileBrowserSilverlightControl',
    {
     top: '30',
     width: '100%',
     height: '100%',
     version: '2.0',
     isWindowless: 'true',
     enableHtmlAccess: 'true'
    },
    {
     onLoad: OnHierarchyChartLoaded
    },
     initParam,
     null);
    }
  }
</script>

Back to the top

Method 1: Add a Content Editor Web Part to the page

Edit the page that contains the Organization Browser web part.
Add a Content Editor Web Part right after the Organization Browser Web Part.
Edit the content.
In the Ribbon, click on HTML/Edit HTML Source under the Format Text tab.
Copy-paste the code above.
Hide the Chrome and the content of the web part so that it would not appear on the page.

Back to the top

Method 2: Edit the page in SharePoint Designer

Please note that this method will detach the page from the site definition, and as such must be used with caution.

Open the page in SharePoint Designer for editing.
Change to code view.
In the Ribbon, click Advanced Mode
Locate the </SharePoint:EmbeddedFormField> tag.
Paste the above code right after the tag.
Save your changes.
Click Yes in the Site Definition Page Warning window.

Back to the top

MORE INFORMATION

Please note that it not possible to overwrite the Html View of the Organization Browser web part from the client. If you need to have a non-Silverlight control available, you will need to write a custom web part to achieve this goal with Windows Claims.

Back to the top

Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use (http://go.microsoft.com/fwlink/?LinkId=151500) for other considerations.

Back to the top