powered by Jive Software

HOWTO: Display full name instead of JID?

I have installed Openfire 3.3.1 for a client using LDAP authentication. They would like to have the e-mail addr () or full name ( ) displayed in the roster instead of the JID. Is this possible?

Any help would be greatly appreciated.

Hi,

usually the client decides what is displayed. Do you map the LDAP fields into the vCard?

Are you using Spark or another client?

LG

it2000 wrote:Hi,

usually the client decides what is displayed. Do you map the LDAP fields into the vCard?

Are you using Spark or another client?

LG

The fields that I’‘m interested in are in the <vcard> section of openfire.xml. I’‘m using Spark, Exodus, SIM, pidgin and GAIM clients for testing. I know it’‘s easy to rename the user in the client, but people being lazy like they are they want the effort done for them. It very well could be that I don’‘t have the <vcard> section setup correctly since I didn’'t make any changes to it. The test option in the AdminConsole does show the information - more or less correctly. I am including my openfire.xml below (santized to protect the guilty).

Thanks!!!

<?xml version=“1.0” encoding=“UTF-8” ?>

  • <!-- This file stores bootstrap properties needed by Openfire.

Property names must be in the format: “prop.name.is.blah=value”

That will be stored as:

<prop>

<name>

<is>

<blah>value</blah>

</is>

</name>

</prop>

Most properties are stored in the Openfire database. A

property viewer and editor is included in the admin console.

–>

  • <!-- root element, all properties must be under this element

–>

  • <jive>

  • <adminConsole>

  • <!-- Disable either port by setting the value to -1

–>

<port>-1</port>

<securePort>9091</securePort>

</adminConsole>

  • <admin>

  • <!-- Use this section to define users that will have admin privileges. Below,

you will find two ways to specify which users are admins. Admins will

have access to the admin console (only local users) and may have also access

to other functionalities like ad-hoc commands.

–>

  • <!-- By default, only the user with the username “admin” can login

to the admin console. Alternatively, you can specify a comma-delimitted

list usernames that should be authorized to login to the admin console

by setting the <authorizedUsernames> field below.

–>

  • <!-- <authorizedUsernames></authorizedUsernames>

–>

  • <!-- Comma-delimitted list of bare JIDs. The JIDs may belong to local

or remote users.

–>

  • <!-- <authorizedJIDs></authorizedJIDs>

–>

<authorizedUsernames>{some admin names from LDAP}</authorizedUsernames>

</admin>

<locale>en</locale>

  • <!-- Network settings. By default, Openfire will bind to all network interfaces.

Alternatively, you can specify a specific network interfaces that the server

will listen on. For example, 127.0.0.1. This setting is generally only useful

on multi-homed servers.

–>

  • <!-- <network>

<interface></interface>

</network>

–>

  • <connectionProvider>

<className>org.jivesoftware.database.DefaultConnectionProvider</classNa me>

</connectionProvider>

<setup>true</setup>

  • <ldap>

<host></host>

<port>636</port>

<baseDN>o=</baseDN> <adminDN>cn=unixmgr,ou=net,ou=,o=</adminDN>

<adminPassword>{password hash}</adminPassword>

<connectionPoolEnabled>true</connectionPoolEnabled>

<sslEnabled>true</sslEnabled>

<ldapDebugEnabled>false</ldapDebugEnabled>

<autoFollowReferrals>true</autoFollowReferrals>

<usernameField>uid</usernameField>

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

<nameField>givenName sn</nameField>

  • <vcard-mapping>

  • <![CDATA[ <vCard xmlns=“vcard-temp”>

<N>

<GIVEN> </GIVEN>
</N>
<EMAIL>
<INTERNET/>
<USERID></USERID>
</EMAIL>
<FN>, </FN>

<NICKNAME></NICKNAME>

<ADR>

<HOME/>

<STREET></STREET>

</ADR>

<ADR>

<WORK/>

<STREET></STREET>

<LOCALITY></LOCALITY>

<REGION></REGION>

<PCODE></PCODE>

</ADR>

<TEL>

<HOME/>

<VOICE/>

<NUMBER></NUMBER>

</TEL>

<TEL>

<WORK/>

<VOICE/>

<NUMBER></NUMBER>

</TEL>

<TEL>

<WORK/>

<CELL/>

<NUMBER></NUMBER>

</TEL>

<TEL>

<WORK/>

<PAGER/>

<NUMBER></NUMBER>

</TEL>

<TITLE></TITLE>

<ORG>

<ORGUNIT></ORGUNIT>

</ORG>

</vCard>

]]>

</vcard-mapping>

<emailField>mail</emailField>

<groupNameField>cn</groupNameField>

<groupMemberField>member</groupMemberField>

<groupDescriptionField>description</groupDescriptionField>

<posixMode>false</posixMode>

<groupSearchFilter>(cn=ITSjabber)</groupSearchFilter>

</ldap>

  • <provider>

  • <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>

  • <database>

  • <defaultProvider>

.

.

<minConnections>5</minConnections>

<maxConnections>15</maxConnections>

<connectionTimeout>1.0</connectionTimeout>

</defaultProvider>

</database>

</jive>

I have the same problem. I think Spark should use nickname instead of username.