SharePoint Anonymouse Access Web Part Targeting

LoginView Control
This control can be used to show content based upon if a users is anonymous or logged in.    In the case below the word “test” would be shown for anonymous users.

Advantages: 
-This would just need to be added to the layout page which is being used for the main portal page.

Issues:
-You cannot put a web part or webpart zone within the control only html which mean you could not use to target web parts to users only html code.
-You cannot edit the content within the browser any updates to your content need to be done in a text editor and pushed to the server during a release.
<tr ID="TopRow" style="padding-top: 6px;padding-right: 6px;padding-left:6px;padding-bottom: 18px;">
 <td valign="top" ID="TopCell" width="100%" colspan="3">
  <asp:LoginView id="LoginView1" runat="server">               
   <AnonymousTemplate>
    <div>Show to Anonymous User</div>
   </AnonymousTemplate>
   <LoggedInTemplate>
    <div>Show to Logged In User</div>
   </LoggedInTemplate>
  </asp:LoginView>
 </td>
</tr>


SP Security Trimmed Control
This control is great for hiding webparts from anonymous users but not from hiding them from logged in users.

Advantages:
-This would just need to be added to the layout page which is being used for the main portal page.

Issues:
-Does not hide webparts from logged in users.
<sharepoint:spsecuritytrimmedcontrol runat="server" permissionsstring="CreateSSCSite">
<webpartpages:webpartzone runat="server" frametype="TitleBarOnly" id="Left" title="loc:Left">
<zonetemplate>
<webpartpages:imagewebpart runat="server" verticalalignment="Middle" allowedit="True" allowconnect="True" connectionid="00000000-0000-0000-0000-000000000000" title="Site Image" isincluded="True" dir="Default" backgroundcolor="transparent" isvisible="True" alternativetext="Microsoft Windows SharePoint Services Logo" allowminimize="True" exportcontrolledproperties="True" zoneid="Left" id="g_60b6aa26_dd7b_4973_aaa0_ece2f2110920" horizontalalignment="Center" imagelink="/_layouts/images/thumbsup.jpg" exportmode="All" allowhide="True" suppresswebpartchrome="False" chrometype="None" framestate="Normal" missingassembly="Cannot import this Web Part." allowremove="True" helpmode="Modeless" frametype="None" allowzonechange="True" partorder="1" description="Use to display pictures and photos." __markuptype="vsattributemarkup" __webpartid="{60B6AA26-DD7B-4973-AAA0-ECE2F2110920}" webpart="true"></webpartpages:imagewebpart>
</zonetemplate>
</webpartpages:webpartzone>
</sharepoint:spsecuritytrimmedcontrol>

SharePoint Anonymous Audience Feature
http://features.codeplex.com/
This is a feature build for SharePoint which adds a check box under the audience settings in all webparts to allow you to directly target them to anonymous users.

Advantages:
-Is automatically integrated into all webparts so it can be used everywhere.
-Web part configuration is done through the browser which means changing a webpart does not require a redeployment.
-When you are logged in and viewing the page in design mode you can still see the webparts that are targeted to anonymous which you are unable to do with the other solutions.

Issues:
Because it is a coded solution it may require review by a Change Control Board before deploying to server.


Comments

Post a Comment

Popular posts from this blog

Add User As Local Administrator On Domain Controller

I recently was settting up a new Microsoft SharePoint 2010 machine and had promoted the machine to a domain controller before creating my SharePoint admin accounts.  I needed to add several of my accounts to the local Administrators group.  Unfortunately after you promote a server to a domain controller you can no longer access the GUI for Local Users and Groups.  Instead I had to use the command line to add the users. Open a command promt using the "Run as administrator" function and then run the following command. net localgroup Administrators /add {domain}\{user} Note: do not include the {} brackets.
Read more

Calling Dataverse Web API in PowerShell using Client Credentials

Image
Connecting to Dataverse using PowerShell can be very helpful for data migrations and use within Azure DevOps. Connecting to an instance in a non-interactive way can be tricky though. This article will provide you the links you need for creation and App registration and adding the app user to your environment. You can then utilize the script provided to call Web API requests including ones you define using the new Custom API functionality now available. The script was written so that it is not dependent on any outside libraries such as the Microsoft.Xrm.Tooling connector. This is helpful in situation where involving an outside library will slow down your deployment time by having to be approved in a change control board. If utilizing an outside code library is not a concern you can create a connection to Dataverse utilizing the Microsoft.Xrm.Tooling connector Get-CrmConnection cmdlet. Create App Registration The first thing to do is create an App Registration within Azure AD for
Read more

Windows Server 2008R2 VMs Shut Down After 1 to 2 Hours

Image
When created a lab environment to test ADFS 2.0 I utilized the Windows 2008R2 VM baselines distributed by Microsoft.  After a few days I was told that I had to activate.  The VMs included a 180 day license for use but I didn't feel like adding another network adapter into Hyper-V to connect them to the internet.  I started having issues though where the servers would shut down every hour or so.  I though that maybe there was a memory issue and Hyper-V was shutting them down in order to free up RAM.  Turns out that if Server 2008R2 is not activated it automatically shuts down after a period of time.  After connecting the server to the internet and activating them the problem went away. Finally the madness of the unknown shut downs has ended :)
Read more