PEP features not showing up (pep)

XEP-0163 states how a client can determine whether their XMPP server supports PEP or not. (section 6)

6. Determining Support
6.1 Account Owner Service Discovery

Naturally, before an account owner attempts to complete any PEP use cases, its client SHOULD determine whether the account owner's server supports PEP; to do so, it MUST send a Service Discovery [19] information request to its own bare JID:

Example 10. Account owner queries server regarding protocol support

<iq from='juliet@capulet.lit/balcony'
    to='juliet@capulet.lit'
    id='disco1'
    type='get'>
  <query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>

If the account owner's server supports PEP and the account is provisioned for PEP, the server MUST return an identity of "pubsub/pep" on behalf of the account (as well as a list of the namespaces and other features it supports, including all supported XEP-0060 features):

Example 11. Server communicates protocol support

<iq from='juliet@capulet.lit'
    to='juliet@capulet.lit/balcony'
    id='disco1'
    type='result'>
  <query xmlns='http://jabber.org/protocol/disco#info'>
    <identity category='account' type='registered'/>
    <identity category='pubsub' type='pep'/>
    <feature var='http://jabber.org/protocol/pubsub#access-presence'/>
    <feature var='http://jabber.org/protocol/pubsub#auto-create'/>
    <feature var='http://jabber.org/protocol/pubsub#auto-subscribe'/>
    <feature var='http://jabber.org/protocol/pubsub#config-node'/>
    <feature var='http://jabber.org/protocol/pubsub#create-and-configure'/>
    <feature var='http://jabber.org/protocol/pubsub#create-nodes'/>
    <feature var='http://jabber.org/protocol/pubsub#filtered-notifications'/>
    <feature var='http://jabber.org/protocol/pubsub#persistent-items'/>
    <feature var='http://jabber.org/protocol/pubsub#publish'/>
    <feature var='http://jabber.org/protocol/pubsub#retrieve-items'/>
    <feature var='http://jabber.org/protocol/pubsub#subscribe'/>
    ...
  </query>
</iq>

However, when I try to do the same none of the above features are returned back to me. My "iq result" is below:

<iq type="result" id="msg_8" to="ucs1@dc3-sw2/ucs" from="ucs1@dc3-sw2">  <query xmlns="http://jabber.org/protocol/disco#info"> 
<identity type="pep" category="pubsub"></identity>
  <feature var="http://jabber.org/protocol/disco#info"></feature>
  <feature var="vcard-temp"></feature>
  <feature var="msgoffline"></feature>
  <feature var="http://jabber.org/protocol/commands"></feature>
</query>
</iq>

This is how my ejabberd.cfg looks:

{modules,
[
{mod_adhoc, []},
{mod_announce, [{access, announce}]}, % requires mod_adhoc
{mod_caps, []},
{mod_configure,[]}, % requires mod_adhoc
{mod_disco, []},
%%{mod_echo, [{host, "echo.dc3-sw2"}]},
{mod_http_bind,[]},
%%{mod_http_fileserver, [
%% {docroot, "/home/arghosh/ejabberd-2.1.3/www"},
%% {accesslog, "/home/arghosh/ejabberd-2.1.3/www/webaccess.log"},
%% {content_types, [{".htm", "text/html"}]},
%% {directory_indices, ["index.html", "index.htm"]}
%%]},
{mod_irc, []},
{mod_last, []},
{mod_muc, [
%%{host, "conference.@HOST@"},
{access, muc},
{access_create, muc_create},
{access_persistent, muc_create},
{access_admin, muc_admin}
]},
%%{mod_muc_log,[]},
{mod_offline, []},
{mod_privacy, []},
{mod_private, []},
%%{mod_proxy65,[]},
{mod_pubsub, [ % requires mod_caps
{access_createnode, pubsub_createnode},
{plugins, ["default", "pep"]}
]},
{mod_register, [
%%
%% After successful registration, the user receives
%% a message with this subject and body.
%%
{welcome_message, {"Welcome!",
"Welcome to this Jabber server."}},

%%
%% When a user registers, send a notification to
%% these Jabber accounts.
%%
%%{registration_watchers, ["admin1@example.org"]},

{access, register}
]},
{mod_roster, []},
%%{mod_service_log,[]},
{mod_shared_roster,[]},
%%{mod_stats, []},
{mod_time, []},
{mod_vcard, []},
{mod_version, []}
]}.

Do I have to add something to ejabberd.cfg so that the pep features show up?

Thanks

Arpan

I see the same problem, so

I see the same problem, so I've reported it in Announce PEP and Pubsub features in account Service Discovery

PEP features not showing up

Does PEP work for you in spite of this?

Thanks

Arpan

Syndicate content