topic Re: LDAP attribute mapping for sync purpose in Alfresco Archive

LDAP attribute mapping for sync purpose

jsabah — Tue, 08 Sep 2009 02:37:10 GMT

Hi all,As I was struggling to find some information on how to map LDAP attributes in Alfresco Authentication files, here is what I found. Hope it helps others.First you need to add the entries you want to map in \Alfresco\tomcat\webapps\alfresco\WEB-INF\classes\alfresco\subsystems\Authentication\com

Re: LDAP attribute mapping for sync purpose

dward — Tue, 08 Sep 2009 10:41:14 GMT

You should never edit the product configuration in WEB-INF, as you will lose all your customizations when you next upgrade.

The correct way to override the Spring configuration of a subsystem is documented here.

http://wiki.alfresco.com/wiki/Alfresco_Subsystems#Spring_Beans

Re: LDAP attribute mapping for sync purpose

dward — Tue, 08 Sep 2009 10:42:35 GMT

Re: LDAP attribute mapping for sync purpose

bnordgren — Thu, 31 Dec 2009 23:06:00 GMT

I had some trouble locating the `qf_name` table in version 3.2r2. However, if I understand the database schema (which is not guaranteed) I believe this SQL query will show the list of attributes present in the content model:

SELECT `alf_qname`.id, local_name
FROM `alf_namespace` , `alf_qname`
WHERE ns_id = `alf_namespace`.id
AND uri = 'http://www.alfresco.org/model/content/1.0'‍‍‍‍

Also, if I'm not mistaken, since we're making <cmerson/> objects out of this, the only attributes which matter must be present as properties in the definition of <cmerson/> (contained in ./WEB-INF/classes/alfresco/model/contentModel.xml). Presumably this xml file must be synced with the hardcoded definition of a person in ContentModel.java. It seems a bit of a maintenance headache to have the same thing defined in three different places, but maybe there is one authoritative source and the rest are autogenerated…

    // person
    static final QName TYPE_PERSON = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "person");
    static final QName PROP_USERNAME = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "userName");
    static final QName PROP_HOMEFOLDER = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "homeFolder");
    static final QName PROP_FIRSTNAME = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "firstName");
    static final QName PROP_LASTNAME = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "lastName");
    static final QName PROP_EMAIL = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "email");
    static final QName PROP_ORGID = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "organizationId");
    static final QName PROP_HOME_FOLDER_PROVIDER = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "homeFolderProvider");
    static final QName PROP_DEFAULT_HOME_FOLDER_PATH = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "defaultHomeFolderPath");
    static final QName PROP_PRESENCEPROVIDER = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "presenceProvider");
    static final QName PROP_PRESENCEUSERNAME = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "presenceUsername");
    static final QName PROP_ORGANIZATION = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "organization");
    static final QName PROP_JOBTITLE = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "jobtitle");
    static final QName PROP_LOCATION = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "location");
    static final QName PROP_PERSONDESC = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "persondescription");
    static final QName PROP_TELEPHONE = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "telephone");
    static final QName PROP_MOBILE = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "mobile");
    static final QName PROP_COMPANYADDRESS1 = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "companyaddress1");
    static final QName PROP_COMPANYADDRESS2 = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "companyaddress2");
    static final QName PROP_COMPANYADDRESS3 = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "companyaddress3");
    static final QName PROP_COMPANYPOSTCODE = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "companypostcode");
    static final QName PROP_COMPANYTELEPHONE = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "companytelephone");
    static final QName PROP_COMPANYFAX = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "companyfax");
    static final QName PROP_COMPANYEMAIL = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "companyemail");
    static final QName PROP_SKYPE = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "skype");
    static final QName PROP_INSTANTMSG = QName.createQName(NamespaceService.CONTENT_MODEL_1_0_URI, "instantmsg");
‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Note that the prefix for "NamespaceService.CONTENT_MODEL_1_0_URI" is hardcoded to "cm" by "PersonServiceImpl.java".

Re: LDAP attribute mapping for sync purpose

loftux — Fri, 01 Jan 2010 13:19:29 GMT

bnordgren,

You should not need to look in the db
tomcat/webapps/alfresco/WEB-INF/classes/alfresco/model/contentModel.xml
and do a search for cmerson, as you did should be enough.
Read http://wiki.alfresco.com/wiki/Data_Dictionary_Guide and you can start exploring the power and extensibility of Alfrescos data model.

The definition in ContentModel.java is for built in data models and to ease the java coding (as avoid making typos for qname), but the data model works independently of this file.

Re: LDAP attribute mapping for sync purpose

bnordgren — Tue, 05 Jan 2010 19:31:55 GMT

Thanks for the pointer. I'm starting to fiddle with it again. I did notice, though, that the XML metadata says the content model is at version 1.1, not 1.0. The content model seems to be out of sync with its own uri… But to fix it, they're going to need to do a global find and replace, searching for every single occurrence of CONTENT_MODEL_1_0_URI. Convenience is in the eye of the beholder, I guess.

Re: LDAP attribute mapping for sync purpose

ifhayz — Fri, 04 Nov 2011 08:02:08 GMT

I've synchronized job title with Windows Active Directory, but job title field can't be edited and the value is null.. I checked to my active directory, job title field is not null…

Could someone give me the solution..?

Regards

Re: LDAP attribute mapping for sync purpose

techguy817 — Thu, 08 Dec 2011 02:46:57 GMT

Can anyone help shed more light on how to get the Active Directory email attribute to map through? I'm trying to use the LDAP Browser to check for properties but I can't figure it out.