AD displayName not showing in Roster

Graeme_Wilson · February 12, 2008, 11:05am

We’re using Openfire 3.4.5 and have configured it to link to our Active Directory (Windows Server 2003). This works well and was really easy to set up but I’m having difficulty configuring Openfire to show the users’ displayName in their roster rather than their account name. For historical reasons our account names are 8 characters and generated by an algorithm. If you don’t know the algorithm it’s difficult to tell who someone is from their account name alone. Users are finding this quite frustrating and it’s hindering take-up of the service. I’ve seen a number of other posts relating to this but have not seen a definitive answer - how can I get Spark to show the displayName in the users’ rosters?

I have attached our openfire.xml but with security settings removed. We have also tried a number of other clients, Pandion, Pidgin etc. and all behave in the same way as Spark. I have also noticed that where we ‘share’ a domain Group the user’s displayName IS shown in the roster, so we’re only having the display name issue where individual users have searched AD and added contacts themselves. However, we don’t want to have to administer Openfire any more than is necessary so sharing all or some of our groups would not be a preferred solution.

Thanks in advance!

sparki · February 12, 2008, 11:40am

Hi,

we have the same setup

try

…

in your openfire.xml and restart

it seems that the clients use the first parameter as the displayname.

NO_MESSAGES_OR_FRIEN · February 12, 2008, 1:32pm

This is the vCard mapping that works with Spark and AD. It Fills in the name fields correctly.

<vcard-mapping><![CDATA[

<N>

</N>

<EMAIL>

</EMAIL>

<ADR>

<HOME/>

</ADR>

<TEL>

<HOME/>

</TEL>

<TEL>

<HOME/>

<CELL/>

</TEL>

<TEL>

<WORK/>

<FAX/>

</TEL>

<TEL>

<WORK/>

</TEL>

<ORG>

</ORG>

</vCard>]]></vcard-mapping>

Graeme_Wilson · February 12, 2008, 1:41pm

Thanks for your suggestions but I can’t see what the difference is between your suggested vcard-mapping and the one in my openfire.xml: both FN and NICKNAME are set to . Is the order of the elements critical? Sparki’s suggestion of moving FN to the first element in the list made no difference for us.

sparki · February 14, 2008, 7:21am

with the setup from mtstravel, which seems to be the default AD setup, we have the problem that all Clients (we use spark, pidgin and miranda) use GIVENNAME as displayname and we have many persons with Michael as givenname. And there is no FAMILYNAME

So I have changed my setup and all fields are now filled in fine. My setup is:

<N>

</N>

<EMAIL>

</EMAIL>

<ADR>

<HOME/>

</ADR>

<TEL>

<HOME/>

</TEL>

<TEL>

<HOME/>

<CELL/>

</TEL>

<TEL>

<WORK/>

<FAX/>

</TEL>

<TEL>

<WORK/>

</TEL>

<ORG>

</ORG>

</vCard>]]>

This works for me with Openfire 3.4.5 Windows2003 and many clients.

NO_MESSAGES_OR_FRIEN · February 14, 2008, 1:34pm

I just realized that my last post had a bad vCard mapping. I do not know how, but it did. This shoould be the correct one:

<vcard-mapping><![CDATA[

<N>

</N>

<EMAIL>

</EMAIL>

<PHOTO>

<TYPE>image/jpeg</TYPE>

</PHOTO>

<ADR>

<HOME/>

</ADR>

<ADR>

<WORK/>

</ADR>

<TEL>

<HOME/>

</TEL>

<TEL>

<WORK/>

</TEL>

<TEL>

<WORK/>

<CELL/>

</TEL>

<TEL>

<WORK/>

</TEL>

<ORG>

</ORG>

</vCard>]]></vcard-mapping>

Graeme_Wilson · February 19, 2008, 1:38pm

Once again, thanks for your suggestions but your vcard-mapping is the same as mine as far as the name related fields go - although I attached my original openfire.xml to my first post I’m also including our current mapping below. What else could be causing Openfire to show the SAMAccountName rather than the displayName in users’ rosters?

<EMAIL>

</EMAIL>

<ADR>

<WORK/>

</ADR>

<TEL>

<WORK/>

</TEL>

<TEL>

<WORK/>

<CELL/>

</TEL>

<TEL>

<WORK/>

<FAX/>

</TEL>

<TEL>

<WORK/>

</TEL>

<ORG>

</ORG>

</vCard>]]></vcard-mapping>

NO_MESSAGES_OR_FRIEN · February 19, 2008, 1:44pm

Let’s expand on the openfire.xml a little:

<usernameField>sAMAccountName</usernameField>

<searchFilter>(objectClass=organizationalPerson)</searchFilter>

<vcard-mapping><![CDATA[

<N>

</N>

<EMAIL>

</EMAIL>

<ADR>

<HOME/>

</ADR>

<TEL>

<HOME/>

</TEL>

<TEL>

<HOME/>

<CELL/>

</TEL>

<TEL>

<WORK/>

<FAX/>

</TEL>

<TEL>

<WORK/>

</TEL>

<ORG>

</ORG>

</vCard>]]></vcard-mapping>

<nameField>givenName</nameField>

<groupMemberField>member</groupMemberField>

<groupDescriptionField>description</groupDescriptionField>

<posixMode>false</posixMode>

<groupSearchFilter>(objectClass=group)</groupSearchFilter>

Graeme_Wilson · February 19, 2008, 2:48pm

The only difference to what I have is that I have <nameField>displayName</nameField>, rather than <nameField>givenName</nameField> as you have. However our rosters could be drawn from 2000+ employees and givenName is not enough to identify the user. How can we use displayName in the roster?

Graeme_Wilson · February 21, 2008, 9:34am

I have found the problem and it is not with Openfire but with Spark.

When I add a contact I’m presented with the attached dialogue showing the jid, the Nickname and the Group that the new contact will be added to. Spark is ignoring the Nickname defined in the vcard and is using the first part of the jid instead - see the attached screenshot. Although I can add the user with the correct display name by clearing the nickname field at this point there are further issues which then prevent me adding the user to my roster correctly. I have tried the same process with Pandion and there are no issues - the user is simply added with the correct display name. Should I continue to expand on this issue in this thread or start a new one under Spark Support?

Jonathon_Taylor · February 26, 2008, 8:09pm

I am having the same trouble with Spark. We use Sun LDAP and have the mappings set properly but when people accept add requests to their roster the nickname is always replaced with the <usernameField> (i.e. uid) and the <NICKNAME> mapping is ignored. Since are user names are meaningless it causes a bit of confusion. Is there a bug open for this on the Spark client side? My config is attached.

<vcard-mapping><![CDATA[

<N>

<ADR>

<HOME/>

</ADR>

<ADR>

<WORK/>

</ADR>

<ORG>

</ORG>

</vCard>]]></vcard-mapping>

<groupMemberField>member</groupMemberField>

<groupDescriptionField>description</groupDescriptionField>

<posixMode>false</posixMode>

</ldap>

<vcard>

<className>org.jivesoftware.openfire.ldap.LdapVCardProvider</className& gt;

</vcard>

<user>

<className>org.jivesoftware.openfire.ldap.LdapUserProvider</className&g t;

</user>

<auth>

<className>org.jivesoftware.openfire.ldap.LdapAuthProvider</className&g t;

</auth>

<group>

<className>org.jivesoftware.openfire.ldap.LdapGroupProvider</className& gt;

</group>

</provider>

<log>

<debug>

<enabled>false</enabled>

</debug>

</log>

</jive>

NO_MESSAGES_OR_FRIEN · February 26, 2008, 8:34pm

in spark if you are manually adding users to your roster the nickname is autoentered as the userid of the username. If you want it to be something else you need to tab to that field and change it before saving the user to your roster. This can be avoided by using shared groups which auto-populate users to the rosters. This will use vCard data to add the names to the roster.

Jonathon_Taylor · February 26, 2008, 9:25pm

Thanks for the explanation. We can’t auto populate our rosters so people use the search feature to find and manually add others to their roster. We have documented the way Spark behaves for our users but it just seems counter intuitive. Especially since when you get an invitation it is the UID and so makes it difficult to know who is really asking to be added to your roster.

NO_MESSAGES_OR_FRIEN · February 26, 2008, 9:27pm

Just because you have me curious, but why can’t you auto-populate the roster?

NO_MESSAGES_OR_FRIEN · February 27, 2008, 2:29pm

Don’t forget to mark this thread as answered (and award any points as merited), so that users know this issue has been resolved.

Graeme_Wilson · February 27, 2008, 3:24pm

I agree with a previous post that this should be raised as a bug in Spark. If the Nickname field is defined in the vcard then it should be used as the Nickname field when adding someone to your roster - otherwise there is no point in having a nickname field and the user might as well rename each entry manually.

How can we get this raised as a bug in Spark?

NO_MESSAGES_OR_FRIEN · February 27, 2008, 4:14pm

I am not sure this is a bug. If you are manually adding users to your roster at that poit spark has no idea if there is an associated vCard or not. That is why it gives you the option to assign a friendly nickname. auto-populated rosters depend on vCards to populate which is why the info is pulled as configured in openfire. I have manually added many users tha have no defined vCard data in the past so therefore would not have a defined nickname. If the user has a vCard after they are manually added you can see that info but it will not override you custom set information from the manual add to roster.

Graeme_Wilson · February 27, 2008, 4:24pm

I am sure it is a bug! When I add a user to my roster using Pandion they are shown in the roster by their Nickname. If I close Pandion and open Spark the user is still shown under their nickname. It is only when I add a user to my roster using Spark that I have this issue. I appreciate that a vcard may not be available in all OpenFire installations but we are linking to Active Directory so there HAS to be a vcard available at the point that I add a user to my roster. Where else is Pandion getting the nickname from? Additionally if I look (in WinXP) at %userprofile%\Spark\user<myjid>\vcards I can see a vcard for everyone on my roster whether they’re there through a published group or whether I have added them to my roster manually. The NickName is correctly stored in this local file however Spark still ignores it and uses the uid.

NO_MESSAGES_OR_FRIEN · February 27, 2008, 4:29pm

Spark is not ignoring the nickname it is using the one you provided when you manually added the user there by overriding what is coming from LDAP. Does the other client give you a field to override the nickname when adding a new user?

NO_MESSAGES_OR_FRIEN · February 27, 2008, 4:33pm

When I add a user manually that is on my AD domain and leave the nickname blank spark pulls the appropriate information from the LDAP vCard. So I guess the answer is to make sure you leave that field blank when manually adding unless you want to override the information provided by LDAP.