13

If you want to do it at page level, you can assign a different master page on "OnPreInit" event. Below is the example to do it on layout page if you have publishing site : public class MyPublishingLayoutPage:PublishingLayoutPage { protected override void OnPreInit(EventArgs e) { base.OnPreInit(e); if (Context....


8

You can enable Anonymous Access by going to Application Management in Central Administration, Highlight the WebApp where you want to enable Anonymous Authentication, Click on Authentication Providers, Click on the Zone where you want to enable Anonymous Access, then Check Enable Anonymous Access, Save. Go to your Web Application and the top level of the ...


7

unfortunately, afaik (& tested) the REST services are only working for authenticated users. You'll need to create a bridge service calling with credentials the native ones if you want to provide that functionality but since you're authenticating your request, are you sure it's not an authentication issue ? Does the target username / password combination ...


7

Make sure that the script files are checked in, published and approved.


7

Unfortunately not. You are only allowed to have one public web site collection in Office 365. If you try to add a subsite to your public site, you'll see the text "This site does not have any subsites." On team sites you can allow sharing with external users who don't need to sign in. In a way, this is anonymous too, but you can't share the entire site ...


7

When giving anonymous access to a publishing portal or a site with the publishing feature activate, there is an additional feature getting activated called ViewFormPagesLockdown. This feature prevents anonymous users from gaining access to certain areas of a site. That includes list forms. From the blog: This feature still exists in SharePoint 2010 and ...


6

If your goal is to have a different look and feel for different users, you can use a single Master Page, and include steps that only target specific profiles (anonymous users in your case). Search the internet for the following terms: SPSecurityTrimmedControl and AnonymousTemplate. It is what I use on this draft page: http://usermanagedsolutions.com For ...


6

One very common workaround I see is that you use an authenticated user to pull the Request that you need, then write it to a document library that allows anonymous access. Because most SP does not accept .json as a file type, just save it as response.txt Then, in your public site, anonymously read from that document library: $.ajax({ url: "/documents/...


5

This is typical when the site collection is a publishing site. Check out http://blogs.msdn.com/b/russmax/archive/2010/01/22/lockdown-mode-in-sharepoint-2010.aspx To determine if a site has ViewFormPagesLockdown enabled run the following: get-spfeature -site http://sitecollectionURL If ViewFormPagesLockDown is listed, it's enabled. To toggle lockdown ...


5

This post describes how can you change masterpage dynamiccally.


5

As a rule of thumb you can say that every URL that ends up in the browser address bar anywhere should be a public URL, therefore a separate zone has to be created. As a good practice, each zone should have its own separate IIS website so you can configure different IIS-related settings like host headers, SSL certificates etc. The public URL is what's being ...


5

If you enable anonymous access to your site (or parts of it), you still need to deactivate “Limited-access user permission lockdown mode” Site Collection Feature if you want those users to be able to dive into Lists or Libraries. Enable anonymous access in “Authentication Providers” (Central Administration > Application Management) Grant rights to ...


4

You can use two options only for targeting content to users (not change of master page): Audience for Server version - http://www.codeguru.com/csharp/.net/net_data/sortinganditerating/article.php/c13255__2/ and for 2010 but the concept seems to be the same in 2010 - http://blog.mastykarz.nl/content-targeting-anonymous-users-sharepoint-server-2010-part2-2/ ...


4

Granted that this is a hosted SharePoint 2010 system I believe we can safely assume that modifying internal pages like _layouts/viewlsts.aspx is a no-go. So, here is another approach taking this into account: Create a new WebPart page and add the view of your list of choice. Repeat this for all lists you want to hide from _layouts/viewlsts.aspx. Open the ...


4

I haven't worked in a lot of anon environments, and it was always my belief that themes were only available once authenticated. If you needed to style something to anon users, you'd need to use a custom master page and/or a custom CSS sheet. When I started to brand http://pirateeric.sharepointspace.com, themes didn't show up when I wasn't logged in so I ...


4

I assume that by saying pages what we created using Visual Studio you mean application pages created in Visual Studio and deployed to _layouts directory. If you want to make such page anonymous, you have to change base class in your code behind. By default, application pages inherit from LayoutsPageBase class, and you have to change it to ...


4

The answer is quite simple. Open the Master Page (Normally V4) Find the following control : <SharePoint:ClusteredSPLinkButton id="idNavLinkViewAllV4" runat="server" PermissionsString="ViewFormPages" NavigateUrl=...


4

You're only option is to contact Microsoft Support in a new service request from the Office 365 Admin Center with your Correlation ID. Ref: How to find more Info on Correlation ID for Office 365 SharePoint Online site These are your support channels in Office 365.


4

By default, SharePoint is secure! Generally, your farm should be up to date with security fixes that bundled with the MU or the CU. Sharegate wrote a good article about How to make SharePoint Secure. that summarized as the following: Run the Microsoft Security Assessment Tool & Best Practice Security Analyzer Tool from Microsoft Only enable the ...


3

You can use an Http Module to accomplish this.


3

You can disable the Access permission to remote interfaces to the anonymous users, follow this: Navigate to the site (or sub-site) where you wish to enable anonymous access. Go to Settings - Site settings. Under Users and Permissions, click on Site Permissions. Under the Permissions tab, click on Anonymous Access. Choose whether you want ...


3

Inspired by this post: https://sharepoint.stackexchange.com/a/36311/17191 I finally got it to work. After: SPList list = web.Lists.TryGetList("Messages"); I've added the line: SPContext renderContext = SPContext.GetContext(HttpContext.Current, null, list.ID, web); and now anonymous user can access a site with this control (without actually having any ...


3

In such situations, the only viable (i.e. open to evolutions) approach would be to deploy an applicative page (or Web service) in _layouts via a WSP. That is, a WSP with server-side code. That page/Web service would hold all the logic/intelligence/business (with elevation if needed, or as the anonymous user to preserve security, but at least you'll be ...


3

"Anonymous" means two things: From a technical point of view (or "identification/who are you?"), you must set "Anonymous" access in IIS. This is for IIS to allow any un-authenticated request to come in, and display the FBA logon page, without IIS interfering for authentication. This means IIS does not handle anymore the authentication through Windows-...


3

RunWithElevatedPrivileges elevates the code block to the Web Application App Pool Account. You need to ensure that account has access to the User Profile Service. I should point out RWEP is generally a bad idea.


3

Try below steps to enable CSOM for Anonymous users: First give permissions at Web application level Steps: Go to Central Administration Go to Manage Web Application Select your Web App Click on Authentication Providers in the ribbon Click zone "Default". Uncheck "Require Use Remote Interfaces Permission" Give permissions on site Steps: Go to Site ...


3

Original post : Anonymous Access: SharePoint 2013 Custom Application Page Try the below steps: Step 1: Open the Central Admin and go to Manage Web Application (under Application Management) . Step 2: Choose the Web Application you want anonymous access for and click on Authentication Provider . Click Default, Default Step 3: Check Anonymous Access ...


2

Anonymous Access Sharepoint 2013 Custom Appliaction Page - Step-1 : Open the Central Admin and go to Manage Web Application (under Application Management) . Step-2 : Choose the Web Application you want Anonymous Access for and click on Authentication Provider . Click Default Step-3 : Check Anonymous Access & Click OK . Step-4 : Open Visual Studio ,...


2

You can go to site pages library, select this page and open list item permission settings. In this settings you can breake role inheritance and remove anonymous access from this list item.


Only top voted, non community-wiki answers of a minimum length are eligible