Article ID: 2643420 - View products that this article applies to.
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.
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.
Method 1: Add a Content Editor Web Part to the page
Method 2: Edit the page in SharePoint DesignerPlease note that this method will detach the page from the site definition, and as such must be used with caution.
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.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2643420 - Last Review: May 14, 2013 - Revision: 6.0