empty allow tokens

[Ahmet Arslan <io...@yahoo.com>]

Hi,

I have a SharePoint 2010 repository connector. I am having this problem with particular share point instance.

Case 1) When I use Authority type: SharePoint 
During indexing, I see some human readable allow tokens inserted :
literal.allow_token_document=ad:UGLOBAL-BILGI%255Cbyo-operasyon-aylik

However when I fire query with fq={!manifoldCFSecurity}&AuthenticatedUserName=GLB90022876@global-bilgi.entp&debugQuery=on
I see allow_token_document:ad:S-1-5-21-1844237615-651377827-725345543-91487 in parsed filter query. And there is no match.


Case 2) When I use Authority type: Active Directory
During indexing, I see literal.allow_token_document=ad: is inserted.
Query time behaviour is same as above. There is no match.


What could be the reason for this? Is it possible to make fq={!manifoldCFSecurity} use human readable allow tokens?


Thanks,
Ahmet

Re: empty allow tokens

[Karl Wright <da...@gmail.com>]

Hi Ahmet,

The problem is how you have configured your authorities.  For your
repository connection, you have specified "SharePoint native", but you have
included the standard "Active Directory" authority.

If you want to use sharepoint native tokens, you will need to replace your
active directory authority with a SharePoint/Native authority instead.
This authority will report all groups associated with users that exist in
the SharePoint instance, rather than in Active Directory.  Alternatively,
if you are using claims-based auth for your SharePoint instance, you would
want both the SharePoint/Native authority AND the SharePoint/AD authority
configured under the same Authority Group.

Hope this helps.
Karl


On Fri, Mar 21, 2014 at 10:42 AM, Ahmet Arslan <io...@yahoo.com> wrote:

> Hi,
>
> I have a SharePoint 2010 repository connector. I am having this problem
> with particular share point instance.
>
> Case 1) When I use Authority type: SharePoint
> During indexing, I see some human readable allow tokens inserted :
> literal.allow_token_document=ad:UGLOBAL-BILGI%255Cbyo-operasyon-aylik
>
> However when I fire query with
> fq={!manifoldCFSecurity}&AuthenticatedUserName=GLB90022876@global-bilgi.entp
> &debugQuery=on
> I see
> allow_token_document:ad:S-1-5-21-1844237615-651377827-725345543-91487 in
> parsed filter query. And there is no match.
>
>
> Case 2) When I use Authority type: Active Directory
> During indexing, I see literal.allow_token_document=ad: is inserted.
> Query time behaviour is same as above. There is no match.
>
>
> What could be the reason for this? Is it possible to make
> fq={!manifoldCFSecurity} use human readable allow tokens?
>
>
> Thanks,
> Ahmet
>