Sharepoint 2013 Create Anonymous Extension - the TRUE and REAL tutorial

so the web is full, with partials tutorials, so the noob me is gonna write the conclusions of 2 half days of suffering (THX MS!). sry for the big pics, i decided to make it ugly but friendly.

1. go to Central Admin, Application Management, Manage web applications. Click on your webApp and then in the ribbon click (on the right) Extend. do the usuall with 2 exceptions: 1st choose allow anonymous, 2nd DONT remove the window authentication not its NTLM checkbox, we will need it yet and remove it in the end. (if u want to be sure click Authentication Providers and choose your new extension and allow all site, but its usually ok unless u changes something).
2. go to you brand new site (you should not touch your admin site - thats only a myth), you should have a ribbon cuz ur authenticated (logged in to SP) go to Site Settings, Site Permissions, you should now see in the ribbon Anonymous Access, click it and the modal should already have chosen Entire Web Site and click OK (if u dont see the ribbon go to http://urNewSiteName/_layouts/settings/aspx). you should now see a new group named anonymous

3. now that is very not enough for sharepoint. now you need to tell him that all kind of different libraries should inherit those permissions. most of them you will find in from this page by clicking the yellow thingy that is saying: well, just read the yellow thingy here:

click it and go library after library (usually only 2) and click on Delete Unique Permissions

3.5 and that is still not enough, there is 1 library he wont tell you about, go to Site Setting, Master Pages and Page Layouts (Mater Pages Gallery), Library Setting, Permissions for this Document Library, and do the same thing.

4. finally u can make ur site anon, go back to Central Admin and back to click on Authentication Providers (if u forgot then go to step 1) and click on the new extension and now unckeck the NTLM only.

Specials:
if u get 500 at some point then the IIS lost his head, do iisreset (from the run window)
if u still get 401 then one of the following:
1 - there is a library that u didnt gave it permissions yet.
2 - u havnt published the page
3 - u try in ur code to do stuff that needs a user like accessing libraries and DBs, use SPSecurity.RunWithElevatedPrivileges(() => //code );

More here http://bresleveloper.blogspot.co.il/2013/04/sharepoint-2010-enable-anonymous-all.html

Comments

Post a Comment

Popular posts from this blog

OverTheWire[.com] Natas Walkthrough - JUST HINT, NO SPOILERS

game portal: http://overthewire.org/wargames/natas/ PASSWORDS for each level are stored in /etc/natas_webpass/natasX I made this walkthrough for people like me, i needed some help, but didnt want the spoiler, so here i will give you all the information needed to pass each level, yet not the solution. For levels needed custom web request i made a different post for powershell and javascript  with how-to's, since is a piece of learning for itself, and also for those of us that play at work and have only powershell at their hands. Although its not a complete spoiler there, its quite most of the solution so try yourself 1st. Natas The Natas game is from basic to advances web hacking. Every few levels is about whole new exploitation (with some harder ones doing comeback later), so a lot of learning. If you're new, you're the reason i am writing so much even for the 1st level, just please google EVERY topic you see, since in the following levels i assume you know the
Read more

SOLVED The item could not be indexed successfully because the item failed in the indexing subsystem

if you got an error like this The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Failed to recover content group; Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 04081656-B51B-4DCD-96D4-6DB2D2CEEEE7 ) as well as these: The item could not be indexed successfully because the item failed in the indexing subsystem. ( The item could not be indexed successfully because the item failed in the indexing subsystem.; Caught exception when preparing generation GID[7]: (Previous generation (last=GID[6], curr=GID[7]) is still active. Cannot open GID[7]); Aborting insert of item in Link Database because it was not inserted to the Search Index.; ; SearchID = 92EB0180-C086-4853-BED8-F4878D9748AD ) the solution for me was to clear configuration cache (PS)  and then restart SP Search Services. THX to m
Read more

Asp.Net Ending Response options, Response.End() vs CompleteRequest()

this blog is for any1 who get the ThreadAbortException when caling Response.End(), and then tried the other options such as HttpContext.Current.ApplicationInstance.CompleteRequest() and found out that there was no replacement. i'll start with the bottom line: if you want to stop right now your response and send it as is you dont have any other option other than Response.End(), period and it's the right thing to throw that EX in that case. the answer is its because there is the "HTTP pipeline" and the "Asp.Net pipeline", and CompleteRequest() cuts the HTTP pipeline but not the Asp.Net one so everything that is from handlers forwars (including all page events) continues but your part, the asp one, stays in your hands so that no information will be lost, so ur suppose to manage your code currectly, since information lost is really a bad thing, although in most cases we use Response.End() we know what we are losing and we want it. see this short article ab
Read more