Return-Path: X-Original-To: apmail-manifoldcf-user-archive@www.apache.org Delivered-To: apmail-manifoldcf-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7B74910C2A for ; Thu, 5 Sep 2013 05:01:00 +0000 (UTC) Received: (qmail 12037 invoked by uid 500); 5 Sep 2013 05:01:00 -0000 Delivered-To: apmail-manifoldcf-user-archive@manifoldcf.apache.org Received: (qmail 11874 invoked by uid 500); 5 Sep 2013 05:00:51 -0000 Mailing-List: contact user-help@manifoldcf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@manifoldcf.apache.org Delivered-To: mailing list user@manifoldcf.apache.org Received: (qmail 11860 invoked by uid 99); 5 Sep 2013 05:00:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 05:00:48 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of parkinson.will@gmail.com designates 209.85.212.182 as permitted sender) Received: from [209.85.212.182] (HELO mail-wi0-f182.google.com) (209.85.212.182) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 05 Sep 2013 05:00:41 +0000 Received: by mail-wi0-f182.google.com with SMTP id ez12so1322413wid.3 for ; Wed, 04 Sep 2013 22:00:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=6WtDu9bn4Ol9DL8E59exbOdSDcY1NDhV0jEBTqHAAKg=; b=rlUBGna8+XUJCrsuzKaht+e2/osyLeD82IW8ZZ+pZ9718v3FXI3AGsnzaSJRJE2GRQ KSEsLPvNTzI9u8Xx7yuPmcQYhEiNrK8zCrQeuJF9yU53f9utIp+Tgn4XsKx9MWPUf19k m7us5nasSImKeKKeTEZjvifbzodSEWMAKf4xo0o07EUe3xRaaeOQwateCm/WPzEyIwe4 J5xy8ziW2klZ8GqdRWpysh7WYPI7HViyZH4PnoqHAx/zmnk7lpjry/QAlYlkNUI0F7ea wt5wNm2Pd47Xki05YLqXYE/xD9RRWemv2CPyI77FM+JMsMjAGIKX/5qqClvUJqASI6sU 7JoQ== MIME-Version: 1.0 X-Received: by 10.181.12.104 with SMTP id ep8mr4763030wid.54.1378357221276; Wed, 04 Sep 2013 22:00:21 -0700 (PDT) Received: by 10.180.10.41 with HTTP; Wed, 4 Sep 2013 22:00:21 -0700 (PDT) In-Reply-To: References: Date: Thu, 5 Sep 2013 15:00:21 +1000 Message-ID: Subject: Re: SID in sharepoint From: Will Parkinson To: user@manifoldcf.apache.org Content-Type: multipart/alternative; boundary=f46d043bdf788c42de04e59bcc45 X-Virus-Checked: Checked by ClamAV on apache.org --f46d043bdf788c42de04e59bcc45 Content-Type: text/plain; charset=ISO-8859-1 Hey Karl, Is the response coming directly from the UserGroup.asmx webservice or by way of the MCPermissions.asmx? Cheers, Will On Wed, Sep 4, 2013 at 9:41 PM, Karl Wright wrote: > This comes from the UserGroup.asmx web service. The sids typically come > from ActiveDirectory. > > The only thing I can conclude is that there are groups in Claim Space that > have no sids. Is this perhaps true? If so, we will need to redefine > access tokens for SharePoint, and a dedicated SharePoint Authority will be > needed to obtain these access tokens given a user. > > Karl > > > > On Wed, Sep 4, 2013 at 7:33 AM, Will Parkinson wrote: > >> Hello >> >> Just wondering if anybody knows where the SID in the XML content >> generated in getSidsForGroup function (SPSProxyHelper.java) originates from >> in Sharepoint? In all cases the SID's are coming out empty >> >> All of my outputs are coming out similar to the following >> >> > ID="23" Sid="" Name="DOMAIN\myuser" >> LoginName="c:0+.w|s-1-5-21-3052554794-3770484871-3874881240-198437" >> Email="" Notes="" IsSiteAdmin="False" IsDomainGroup="True" >> Flags="0"/> >> >> The SID is necessary for to obtain the correct ACL's it seems. >> >> Any info is much appreciated. >> >> Cheers, >> >> Will >> > > --f46d043bdf788c42de04e59bcc45 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hey Karl,

Is the response coming directly from= the UserGroup.asmx webservice or by way of the MCPermissions.asmx?

=
Cheers,

Will


On Wed, Sep 4, 2013 at 9:41 PM, Karl Wright <daddywri@gmail.com>= wrote:
This comes from the UserGroup.asmx web service.=A0 Th= e sids typically come from ActiveDirectory.

The only thing I c= an conclude is that there are groups in Claim Space that have no sids.=A0 I= s this perhaps true?=A0 If so, we will need to redefine access tokens for S= harePoint, and a dedicated SharePoint Authority will be needed to obtain th= ese access tokens given a user.

Karl



On Wed, Sep = 4, 2013 at 7:33 AM, Will Parkinson <parkinson.will@gmail.com>= ; wrote:
Hello

Just wondering if anybody knows where the SID in the XML content generate= d in getSidsForGroup function (SPSProxyHelper.java) originates from in Shar= epoint?=A0 In all cases the SID's are coming out empty

All of my outputs are coming out similar to the following
<ns1:GetUserCollectionFromGroup xmlns:ns1=3D"http:/= /schemas.microsoft.com/sharepoint/soap/directory/"><ns1:User= s><ns1:User ID=3D"23" Sid=3D"" Name=3D"DOMAI= N\myuser" LoginName=3D"c:0+.w|s-1-5-21-3052554794-3770484871-3874= 881240-198437" Email=3D"" Notes=3D"" IsSiteAdmin= =3D"False" IsDomainGroup=3D"True" Flags=3D"0"= /></ns1:Users></ns1:GetUserCollectionFromGroup>

The SID is necessary for to obtain the correct ACL's it = seems.

Any info is much appreciated.

Cheers,
Will


--f46d043bdf788c42de04e59bcc45--