Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

This is the current situation:

  • We've setup a SharePoint website with 2 types of users: Visitors and Admins.
  • The role of a visitor is that they're only able to see the webpages (no document/library involvement), the role of an administrator is like 'full access'.

A few days ago, the SharePoint site was working like it was supposed to. Visitors were able to see the webpages without any authentication of an login prompt. I've checked the permissions of the default.master page and these are setup correct.

Is there a way to fix this?

share|improve this question
    
So your new situation is, that suddenly all visitors needs authentification as visitors as well as admins needs to do this all day long? –  Shegit Brahm Jun 25 '12 at 7:00
    
Yes, sorry if it wasn't defined enough. –  BenCes Jun 25 '12 at 7:12
    
Can you confirm if this issue occurs for Site Collection Administrators as well and not just for people with 'Full Control' –  Arko D Jun 25 '12 at 7:20
    
Don't you change anything to your browser policy? I mean the sharepoint site is still in trusted ones? Do you tried to change the security behaviour in IE? –  Seb Jun 25 '12 at 8:29

2 Answers 2

Did you change anything recently ?

  • Any Master page updated but not published / approved ?
  • Any Page layout updated but not published / approved ?

Is it occuring on all pages or only on some page ? Did you add a web / user control recently that could require more permissions than what is available for the anonymous user ?

Do you still have your binding under the IIS site ? It will be the first one to challenge you (another site might have *:80 which could take the lead depending on order).

You should fire up Fiddler to see which request and which asset is triggering the authentication. It might be a single (unpublished) image referenced in the master page or a webpart that is forcing a request.

share|improve this answer
    
Yes I did some updates, but I haven't touched the user policy. The website isn't located in the Trusted Websites List but that wasn't a problem at all before this problem (IE was asking for login, other browsers just showed the website as normal visitor.) –  BenCes Jun 25 '12 at 11:49
    
Have you touched the Alternate Access Mappings, do you have a URL for the Internet zone? What zone are your users hitting? –  pigeon Jun 25 '12 at 13:06
    
Never touched the Alternate Access Mappings before. The users are only hitting the normal webpages in the Shared Documents section. There is no interaction on documents or something with the normal user. –  BenCes Jun 25 '12 at 14:31
    
Edited my reply to suggest using Fiddler to check which resource is triggering the authentication handshake –  Francois Verbeeck Jun 25 '12 at 15:20
    
Is there a way tho check this with Firefox's WebConsole? (A webdeveloppper application inside Firefox). I can catch the authentication event: i46.tinypic.com/2lb0wfq.png but I haven't got a clue which item on my default is causing this. –  BenCes Jun 27 '12 at 7:01
up vote 0 down vote accepted

This was the problem:

  • A calendar that was placed on the defaultpage wasn't accesable by 'anonymous acces'.
  • Changed this to 'show elements' and the problem was solved.
share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.