Quantcast
Channel: LDAP/AD Claims Provider For SharePoint
Viewing all 270 articles
Browse latest View live

New Post: How to keep admin pages while customizing ldapcp?

$
0
0
Thank you for your answer. In fact I just need to make the people picker displays the 'User display name'.

Could you be kind enough to show me how to modify the custom code following (downloaded from this site) to achieve this?
        protected override void SetCustomConfiguration(Uri context, string[] entityTypes)
        {
            //base.SetCustomConfiguration( context, entityTypes);

            this.CurrentConfiguration.FilterEnabledUsersOnlyProp = true;
            this.CurrentConfiguration.FilterSecurityGroupsOnlyProp = true;
            this.CurrentConfiguration.FilterExactMatchOnlyProp = false;

            // If input is resolved by an attribute linked to identity claim type (typically displayName and cn attributes), show its value in parenthesis.
            this.CurrentConfiguration.DisplayLdapMatchForIdentityClaimTypeProp = false;

            // By default LDAPCP matches LDAP attributes with claim types as documented in homepage of project
            // But you can customize this mapping to match claim types defined in (Get-SPTrustedIdentityTokenIssuer).ClaimTypeInformation
            this.CurrentConfiguration.AttributesListProp = new List<AttributeHelper>
            {
                new AttributeHelper{LDAPAttribute="mail", LDAPObjectClassProp="user", ClaimType=WIF.ClaimTypes.Email, ClaimEntityType = SPClaimEntityTypes.User, EntityDataKey=PeopleEditorEntityDataKeys.Email,LDAPAttributeToDisplayProp="DisplayName"},
                new AttributeHelper{LDAPAttribute="sAMAccountName", LDAPObjectClassProp="user", ClaimType=WIF.ClaimTypes.WindowsAccountName, ClaimEntityType = SPClaimEntityTypes.User, AdditionalLDAPFilterProp="(!(objectClass=computer))",LDAPAttributeToDisplayProp="DisplayName"},
                new AttributeHelper{LDAPAttribute="userPrincipalName", LDAPObjectClassProp="user", ClaimType=WIF.ClaimTypes.Upn, ClaimEntityType = SPClaimEntityTypes.User,LDAPAttributeToDisplayProp="DisplayName"},
                new AttributeHelper{LDAPAttribute="sAMAccountName", LDAPObjectClassProp="group", ClaimType=WIF.ClaimTypes.Role, ClaimEntityType = SPClaimEntityTypes.FormsRole,LDAPAttributeToDisplayProp="DisplayName"},

                // Items below (CreateAsIdentityClaim=true) will always be queried and permission will be created using identity claim type
                // This allows to search user on common attributes such as the firstname / lastname / displayname, etc...
                new AttributeHelper{LDAPAttribute="displayName", LDAPObjectClassProp="user", CreateAsIdentityClaim=true, EntityDataKey=PeopleEditorEntityDataKeys.DisplayName,LDAPAttributeToDisplayProp="DisplayName"},
                new AttributeHelper{LDAPAttribute="cn", LDAPObjectClassProp="user", CreateAsIdentityClaim=true, AdditionalLDAPFilterProp="(!(objectClass=computer))",LDAPAttributeToDisplayProp="DisplayName"},
                new AttributeHelper{LDAPAttribute="sn", LDAPObjectClassProp="user", CreateAsIdentityClaim=true,LDAPAttributeToDisplayProp="DisplayName"},

                // items below don't have a claim type or CreateAsIdentityClaim set, so they do not participate in LDAP query, but they are retrieved (if they exist) to populate metadata (PeopleEditorEntityDataKeys) of the permission (PickerEntity)
                new AttributeHelper{LDAPAttribute="department", LDAPObjectClassProp="user", EntityDataKey=PeopleEditorEntityDataKeys.Department,LDAPAttributeToDisplayProp="DisplayName"},
                new AttributeHelper{LDAPAttribute="title", LDAPObjectClassProp="user", EntityDataKey=PeopleEditorEntityDataKeys.JobTitle,LDAPAttributeToDisplayProp="DisplayName"},
            };
        }

New Post: Problem to deploy ldapcp custom in vstud 2015

$
0
0
Hello,

Could anybody help me with the following issue?

I dowloaded the developper last version of ldapcp. When deploying I get the following error.
I deploy the project with visstudio 2015 as administrator on sharepoint 2013.

Kind regards.
Claude
------ Rebuild All started: Project: LDAPCP 2013 for Developers, Configuration: Debug Any CPU ------
  LDAPCP 2013 for Developers -> D:\dvpl\LDAPCP 2013 for Developers_last\LDAPCP 2013 for Developers\LDAPCP 2013 for Developers\bin\Debug\LDAPCP 2013 for Developers.dll
  The system cannot find the path specified.
C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(4713,5): error MSB3073: The command ""C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\x64\gacutil.exe" /f /i "D:\dvpl\LDAPCP 2013 for Developers_last\LDAPCP 2013 for Developers\LDAPCP 2013 for Developers\bin\Debug\LDAPCP 2013 for Developers.dll"" exited with code 3.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========

New Post: How to keep admin pages while customizing ldapcp?

$
0
0
Then you can type just this in the method;
this.CurrentConfiguration.AttributesListProp = new List<AttributeHelper>
{
    new AttributeHelper{LDAPAttribute="userPrincipalName", LDAPObjectClassProp="user", ClaimType=WIF.ClaimTypes.Upn, ClaimEntityType = SPClaimEntityTypes.User},
};
Well, of course you must replace WIF.ClaimTypes.Upn with the actual identity claim type set in the trust.

New Post: Problem to deploy ldapcp custom in vstud 2015

$
0
0
Hello,
it's just the post-build event that doesn't find gacutil.exe (used to copy assembly in the GAC), which is probably in a different path.
You can either fix the path or remove the command, in LDAPCP Project properties > Build Events > Post-build event command line.
thanks,
Yvan

New Post: How to keep admin pages while customizing ldapcp?

$
0
0
Thank you, you mean to have just the code below in the "SetCustomConfiguration" method?
protected override void SetCustomConfiguration(Uri context, string[] entityTypes)
{
   this.CurrentConfiguration.AttributesListProp = new List<AttributeHelper>
   {
       new AttributeHelper{LDAPAttribute="userPrincipalName", LDAPObjectClassProp="user", ClaimType=WIF.ClaimTypes.Upn, ClaimEntityType = SPClaimEntityTypes.User},
   };
}
Thank you
Claude

New Post: How to keep admin pages while customizing ldapcp?

$
0
0
Hello Yvand,

I did it and what is displayed is not the display name but the upn. How can I manage to only show the Display name in the picker when users are proposed to be picked up?

I tried something like below without success...still the upn is showed...

new AttributeHelper{LDAPAttributeToDisplayProp="displayName" }

Kind regards.
Claude

New Post: How to keep admin pages while customizing ldapcp?

$
0
0
Hello,
you just need to set property LDAPAttributeToDisplayProp like this:
protected override void SetCustomConfiguration(Uri context, string[] entityTypes)
{
   this.CurrentConfiguration.AttributesListProp = new List<AttributeHelper>
   {
       new AttributeHelper{LDAPAttribute="userPrincipalName", LDAPObjectClassProp="user", ClaimType=WIF.ClaimTypes.Upn, ClaimEntityType = SPClaimEntityTypes.User, LDAPAttributeToDisplayProp="DisplayName"},
   };
}

New Post: How to keep admin pages while customizing ldapcp?

$
0
0
It works!

Thank you very very very much Yvand.

Kind regards.
Claude

New Post: LDAP Connection - UserName

$
0
0
Is it possible to query a domain that uses an account in a different domain (Just like in User Profile Sync Service)? We use a single service account to connect to all domains.

New Post: LDAP Connection - UserName

$
0
0
Sure, the LDAPCP global settings page lets you specify the credentials to use when you add a new LDAP connection

Created Unassigned: error when add sp solution with powershell on SP2013 [2540]

$
0
0


when trying to add the wsp solution package with Powershell , the following error is received on the sp 2013 farm server standalone server

add-SPSolution -LitteralPath "c:\tools\LDAPCP.wsp"

Add-SPSolution : Solution manifest for solution '6ff99767-b95a-4143-8cd8-3978aa01fb80' failed validation, file manifest.xml, line 1276, character 8: The
'http://schemas.microsoft.com/sharepoint/:l' element is not supported in this context.
At line:1 char:1
+ Add-SPSolution -LiteralPath $lacppath
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...dletAddSolution:SPCmdletAddSolution) [Add-SPSolution], SPException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletAddSolution


any idea why is this happening

New Post: LDAPCP 2013 for Developers

$
0
0
Hi all,

Can someone provide an example how to associate LDAP with more than one SPTrustedIdentityTokenIssuer?
I really dont know what to do in the LDAPCP 2013 for Developers project.

Some people said that we have to redefine a method called SetLDAPConnections but I cant find that method in the VS project.

Thanks.

Commented Unassigned: error when add sp solution with powershell on SP2013 [2540]

$
0
0


when trying to add the wsp solution package with Powershell , the following error is received on the sp 2013 farm server standalone server

add-SPSolution -LitteralPath "c:\tools\LDAPCP.wsp"

Add-SPSolution : Solution manifest for solution '6ff99767-b95a-4143-8cd8-3978aa01fb80' failed validation, file manifest.xml, line 1276, character 8: The
'http://schemas.microsoft.com/sharepoint/:l' element is not supported in this context.
At line:1 char:1
+ Add-SPSolution -LiteralPath $lacppath
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...dletAddSolution:SPCmdletAddSolution) [Add-SPSolution], SPException
+ FullyQualifiedErrorId : Microsoft.SharePoint.PowerShell.SPCmdletAddSolution


any idea why is this happening

Comments: I never saw this error before, did you try to download it again?

New Post: LDAPCP 2013 for Developers

$
0
0
Hello,
In LDAPCP 2013 for Developers project you can find multiple classes that inherit LDAPCP, each creating a unique version with some different customization.
The need to inherit is mainly to specify a new name for the claims provider, since it acts as a unique identifier in SharePoint.
Hopefully the various examples should guide you, but you can stick to LDAPCP_Custom, which is the simplest one.
But you really need devleoper skills for that

New Post: LDAPCP 2013 for Developers

$
0
0
Thanks for your response.

I only change the _ProviderInternalName name from "LDAPCP_Custom" to something else and associate this provider to other SPTrustedIdentityTokenIssuer.
I have 2 SPTrustedIdentityTokenIssuer with one associate with the "LDAPCP" and other with "LDAPCP_Custom" but it doesnt work.

It should work with only the ProviderInternalName changed? Or I need to override other methods?

If I had only deployed the "LDAPCP" it works like a charm.
Thank you Yvan for the hard work that you put in this beautiful custom provider.

New Post: LDAP Connection - UserName

$
0
0
I've entered the account using both domainName\AccountName & the upn (i.e. abc@domain.local) but both fail. Is there a particular checkbox or format that I need to use?

New Post: LDAP Connection - UserName

$
0
0
To assist others with this issue. You must place a check next to "Secure" in order to use an account that is not in the domain that you're connecting to for LDAP. This is an awesome product and has saved me countless hours. Best regards!

New Post: LDAP Connection - UserName

New Post: LDAPCP 2013 for Developers

$
0
0
Yes, that's the only mandatory change to make.
Do you see your custom LDAPCP when you run cmdlet Get-SPClaimProvider?
Do you see the farm feature of your custom LDAPCP in cemtran administration? Is it activated?

New Post: How to keep admin pages while customizing ldapcp?

$
0
0
Hello and Beste wishes for the new year to all.

A remaining question about the display of the results.
Is there a way to display not only the dispay name of the found users but to add too the name of the AD group they belongs to?
Kind regards.
Claude
Viewing all 270 articles
Browse latest View live


Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>