Here is the relevant section of the sm.xml file if it helps:
<user>
<!-- By default, users must explicitly created before they can start
a session. The creation process is usually triggered by a c2s
component in response to a client registering a new user.
Enableing this option will make it so that a user create will be
triggered the first time a non-existant user attempts to start
a session. This is useful if you already have users in an
external authentication database (eg LDAP) and you don't want
them to have to register. -->
<auto-create/>
<!-- Define maximum size in bytes of fields of vcards.
There is a recommendation that the avatar picture SHOULD NOT
be larger than 16 KiB. -->
<!--
<vcard>
<max-field-size>
<default>16384</default>
<avatar>16384</avatar>
</max-field-size>
</vcard>
-->
<!-- Templates. If defined, the contents of these files will be
stored in the users data store when they are created. -->
<template>
<!-- Uncomment <publish> if you wish to forcely publish
roster template from ldap on each user login -->
<publish>
<!-- If <check-remove-domain> given, then published contact checked
against sm user database and if user is unknown to sm,
contact
will be deleted from user's roster (if it is in roster). -->
<!--
<check-remove-domain></check-remove-domain>
-->
<!-- Keep cache of "active" database specified number of seconds.
This will significantly speed up publishing of roster.
If unspecified or 0, no cache is used. -->
<active-cache-ttl>60</active-cache-ttl>
<!-- If <fix-subscriptions/> is not commented, set subscriptions of
user's contacts to subscriptions of corresponding published
contacts. As for now, "both". -->
<!--
<fix-subscriptions/>
-->
<!-- If <override-names/> is not commented, then displayed names of
contacts in user's roster will be updated accordingly to
published roster (if they differ). If commented, then user can
rename contacs in roster -->
<override-names/>
<!-- when mapped-groups is on (<map-groups/> is uncommented, the
actual
group names for published contacts are read from
published-roster-groups storage type, which in turn may be
mapped
to ldapvcard driver. The key for searching is published user's
group, and returned value is used as group name. So you can
assign
textual group IDs to users rather then group names.
group-cache-ttl keeps cache of mapping group id <-> group
name for
specified number of seconds. If unspecified or 0, no cache
is used.
-->
<!--
<mapped-groups/>
<map-groups/>
<group-cache-ttl>120</group-cache-ttl>
</mapped-groups>
-->
<!-- If <force-groups> is commented out, published roster's contact
added to user's roster only when user does not have this
contact.
If <force-groups> is not commented out, then these checks
performed
against roster item when publishing roster item that already in
user's roster:
If user already has added his roster's contact to group of
published contact, no changes are made with this group (note
that contact may be in more than one group).
If <prefix> given, then prefix of each group of user's
compared
whith given prefix, and if it matches, user's contact
removed from
matched group (see below).
Same for <suffix>.
After that, user's contact added to a group of published
roster's
contact.
In other words, all groups of updated contact, that match
prefix
or suffix, replaced with group of published contact.
This is done because there is no way to determine that
group was
published or greated by user. -->
<!--
<force-groups>
<prefix>MyOrg.</prefix>
<suffix>(MyOrg)</suffix>
</force-groups>
-->
</publish>
<!-- If you defined publish, you should comment <roster> -->
<!--
<roster>/usr/local/etc/templates/roster.xml</roster>
-->
</template>
</user>
(Sorry about the return receipt on the last email, I have a default
policy for this email since it is hard to tell who here reads there
email, fixed that on this email though.)
-Ian
Ian McInerney wrote:
Ok, so far I have gotten it so that the server is connecting to the
LDAP server to pull the roster data, except the roster is still not
being pushed out to the individual users. I look at the debug output
of the server and see these lines:
SM : Wed Oct 28 10:26:31 2009 mod_roster_publish.c:220 publishing
roster for [email protected]
SM : Wed Oct 28 10:26:31 2009 storage.c:222 storage_get:
type=published-roster owner= filter=(null)
SM : Wed Oct 28 10:26:31 2009 mm.c:449 calling module roster
so it appears that it is calling the roster_publish module, but that
the roster itself is not being created. Is there anything specifically
I have to do to create the roster on server startup or should it
automatically be created?
-Ian
--
Ian McInerney, KC9MVU
Junior, Illinois Mathematics and Science Academy
[email protected]
"Live Long and Prosper", Leonard Nimoy
No electrons were harmed in the making of this message.
--
To unsubscribe send a mail to [email protected]
