This project has moved. For the latest updates, please go here.

Anyone successfully deployed the Developer Samples?

Jan 7, 2015 at 10:51 PM
As far as I can tell you cant get the LdapcpSettings.aspx page to deploy unless you deploy ldapcp.wsp (now you can see the custom actions for LDAPCP in CA. After deploying that you can then deploy your custom wsp from the developer samples. At that point you have two different claim providers in SharePoint which is fine/supported as long as the names are unique. Next, you can safely update your token issuer to point to your custom developer sample like so:

$trust = Get-SPTrustedIdentityTokenIssuer $tokenissuer
$trust.ClaimProviderName = "LDAPCP_CustomPermissionValue"

However the LdapcpSettings.aspx has a line of code in it whereby it assumes that the only claim provider it can use is: "LDAPCP" because it does this:

CurrentTrustedLoginProvider = LDAPCP.GetSPTrustAssociatedWithCP(LDAPCP._ProviderInternalName);
if (null == CurrentTrustedLoginProvider)
// error

_ProviderInternalName will be "LDAPCP" and not your derived provider. The only way around this is to recompile the LDAPCP source.

What techniques short of recompiling is anyone using.
Jan 9, 2015 at 7:18 PM
How about a different way of wording it. Does anyone know if when you use the developer samples, you're not supposed to have the claim list and settings pages by design. Maybe you're only supposed to install the custom WSP and not both the custom and the base wsp. All configuration has to be programmatically added and there is no UI support. Correct?
Jan 12, 2015 at 11:32 AM
I can confirm that you cannot use the admin pages when you use the developer solution, every customization must be done programmatically.