Hi Lee,
Thanks.
I've gotten as far as narrowing the problem down to ADAM not being able to
create foreignSecurityPrincipals with an authority other than 5, that is not
the "S-1-9-xxx" that I wanted for my custom SID.
Someone with Microsoft is checking whether this is solved in R2 (with
reference to some bug report), but I guess you already showed that.
I will change my code to produce S-1-5-* SIDs instead, even though it seems
a bit hacky (seems that authority 5 is for AD, NT4 domains and LSA?)
But thanks for figuring it out - even though my client is in no position to
upgrade to a beta of R2.
Niels
> Hi
>
[quoted text clipped - 23 lines]
> cn: TestGroup1
> member:
ADAM store:> store.Initialize> (0, "msldap://localhost:50000/CN=Store,CN=AzManTest,DC=PKA> ,DC=DK", null);>> // it works with this AD store:> // store.Initialize> (0, "msldap://cn=AzManStore,CN=Program> Data,DC=CITEST,DC=cinetworks,DC=net", null);>>> IAzApplicationGroups azGroups => store.ApplicationGroups;> foreach (IAzApplicationGroup> azGroup in azGroups)> {> azGroup.AddMember(sid,> null);> azGroup.Submit(0, null);> }> }>>> }> }>