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

Something happened in the course of two days where all claims users are getting access denied.

This is what my claims id looks like when looking at policy for web application (it has full control and will always get access denied): policyforwebapp

But when I log in with NTLM, and put the all authenticated users group to have access, this is what my claims id looks like (after logging in with claims):

enter image description here

Perhaps this isn't a problem but I was expecting the same prefix. Ideally,I would like to read on where the prefix comes from as well. the 't' stands for Trusted STS, c stands for other claims, 5 is for email address, but where does that 'g' come from? Is it possible that my people picker is selecting the wrong person?

I used to have object cache errors, so those have been resolved: http://blogs.msdn.com/b/andrasg/archive/2010/09/30/setting-the-super-user-account-on-sharepoint-2010-and-getting-access-denied-errors-afterwards.aspx

What I'm left with is possibly following this article for troubleshooting since it sounds like there is a problem with the claims that are being created. http://blogs.technet.com/b/speschka/archive/2010/02/13/figuring-out-what-claims-you-have-in-sharepoint-2010.aspx

Is there anything else that I can read to help troubleshoot this? Thanks

share|improve this question
    
found out the g is custom claims provider, duh –  bitterac May 8 '13 at 17:45
    
Wictor explains the encoding here: wictorwilen.se/Post/… –  Paul Schaeflein May 8 '13 at 17:47
    
Your screen shot has an accent over the g. Not sure how, but usually that is an encoding (Unicode) mismatch. –  Paul Schaeflein May 8 '13 at 17:49
    
yeah, I thought it was strange too but it is expected. confirmed with the wictor post –  bitterac May 8 '13 at 18:48
    
I get 'Access Denied: Authentication is required' messages in the ULS logs. So I'm going to chalk this up to DNS issues accessing the ADFS server. –  bitterac May 8 '13 at 21:20
show 1 more comment

Your Answer

 
discard

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

Browse other questions tagged or ask your own question.