Issue with the Claim Augementation about ldapcp

[Yvand]

Hi @eduralph, nice catch, thank you for reporting it.
The scenario is not completely clear to me.
Do you repro on SharePoint 2013 or 2016?
Do you repro with a trusted user or a WinClaims user can repro that too?

[eduralph]

Hi Yvand,

sorry if I wasn't clear. We caught it on SharePoint 2013 and as far as I can see it happened exclusively with Forms-based users using Active Directory as repository for these in a Claims-based environment. I couldn't see this happening in scenarios with ADFS (trusted users) or Negotiate (WinClaims). We didn't validate this on a 2016 environment either. We solved the problem by turning off the Augmentation, so I can't follow-up on that....

[Yvand]

Hi @eduralph, thank you for the additional info.
I can change the code to fix this even with augmentation enabled: instead of doing elevation of privileges immediately, I can first verify if incoming user is a federated user (so it must be augmented) or not (so nothing to do).
At first glance it's very easy to do. If I don't find any side effect I will put this change in the next release.

[Yvand]

It's fixed in v10