Tag Info

Hot answers tagged

12

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 ...


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 ...


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 ...


5

Why are you deploying your Custom Web Service to the layouts folder at first place? You need to copy the Web service files to the _vti_bin virtual directory Copy the Service1wsdl.aspx file, the Service1disco.aspx file, and the Service1.asmx file to the _vti_bin virtual directory. This is the directory where all default Web services are stored. Copy the ...


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

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 ...


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

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


4

Do you have multiple zones on your web application? If so, try calling the web service on a zone that does not have Anonymous access enabled. I came across this post a while back that shed some light onto it. http://chrisdomino.com/Blog/Post/401-Reasons-Why-SharePoint-Web-Services-Don-t-Work-Anonymously?Length=4


4

You could a a location tag to the web.config, restricting access to logged in (admin) users only. <location path="PATHTOUSERINFOLIST"> <system.web> <authorization> <allow roles="Admin"/> <deny users="?"/> </authorization> </system.web> </location>


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

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

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 ...


3

I'm not that familiar with the Chart web part but from checking it out my guess is that it have the same issues with anonymous user as client object model based web parts (like Silverlight based web parts) have. The problem is that by default SharePoint restrict the GetItems method of SPLIst for anonymous users. You should check out Waldek Mastykarz's post ...


3

You can enable lockdown mode to prevent unauthenticated users from accessing list and library pages. Or, if it is indeed only one page that you want to allow, then you can add the following to your web.config: <configuration> <system.web> <authorization> <deny users="?" /> </authorization> ...


3

Internet Options -> Security Tab -> Local Intranet -> Custom Level -> Scroll to the bottom. User Authentication section set Logon option to Anonymous Also with the Intranet section highlighted, you can deselect Automatically detect intranet network and remove any instances of your Sharepoint URL from the Advanced menu in the Sites area. This might not be ...


3

You can use an Http Module to accomplish this.


3

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 ...


3

Inspired by this post: http://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

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


3

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 ...


2

Have a look at this blog post I wrote last week and see if this helps. This doesn't permission the physical file, but you can use this technique to determine if you should show or not show content or a nav link based on the user. http://mike-greene.com/?p=309


2

Another similar scenario is described here with a solution http://kwizcom.blogspot.com/2007/06/anonymous-users-cannot-access-list.html


2

Or, in Powershell: $wa = get-spwebapplication http://{url} $zone = [Microsoft.SharePoint.Administration.SPUrlZone]::Extranet $i = $wa.IisSettings[$zone] $i.AllowAnonymous = $true $wa.Update() $wa.ProvisionGlobally() $w = Get-SPWeb http://{url} $w.AnonymousState = [Microsoft.SharePoint.SPWeb+AnonymousState]::On $w.Update() $l = $w.Lists["Comments"] ...


2

Have you checked-in and published the custom master page?


2

I recognise I posted this question a while ago now, but having just seen Jim's answer it reminded me of something I'd seen a couple of months ago... In the August Cumulative Update for SharePoint 2010 Foundation one of the areas it mentions a fix for is: Anonymous users cannot use Language Integrated Query (LINQ) to query data in Microsoft ...


2

I discovered what was going on. With the configuration I had, the main site was a publishing web. The blog site was a sub-site from the publishing web. The fact that the publishing web was enabled led to permissions problems for the blog site. What I ended up doing was creating a new site collection that only has the blog site within it. Setting up ...


2

Christophe, I think I answered by email as well, but in any case, here's a brief blog post that explains how and why: http://blog.furuknap.net/enabling-declarative-workflows-for-anonymous-users-in-sp20102007 .b


2

The plumbing to handle anonymous/unauthenticated users already exists within SharePoint...you don't need to re-create it by logging them in to what in affect would be another anonymous (...guest) account. If you're going to log anonymous users in to let them access the site then just enable anonymous access and go thru and grant them access to the pages, ...



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