I have a SharePoint site which is setup with claims based authentication. My Central Admin site is setup for Windows authentication as it normally is.
Now in my ULS logs, I find a lot of messages like:
No windows identity for DOMAIN\user
When you look this up, there are multiple explanations which I've checked all, without any luck.
What I think is, that my default content access account, which is configured as DOMAIN\user causes trouble with my claims based site. Finding a Windows Identity for a claims based site would only work for a claims based account I suppose.
If that makes sense, it would also make sense to set a claims based account as the content access account, right? Well that's easier said then done apparantly. When I enter a claims based name, the form says it's invalid. That could be because the central administration isn't claims based? The weird thing is that I have multiple authentication providers configured which I can use without problem in other parts of Central Administration.
I searched if there's a way to do so in Powershell, but didn't find a promising one. The SetDefaultGatheringAccount method takes a username and a password, so not a real good way to set a claims based account?
So my questions; 1) Is is better to use a claims based content access account to crawl claims based sites? 2) Is is possible to set a claims based content access account? 3) If so: how?