Any way to enable jabber:iq:browse and jabber:iq:agents?

Openfire Openfire Support
#21

@guus This is what the trace log says when I make a request (from the bottom up):

2023.01.16 19:33:24 TRACE [socket_c2s_ssl-thread-2]: org.jivesoftware.openfire.plugin.IQAgentInformationHandler - Perform disco#info request on facebook.my.xmpp.server on behalf of user@my.xmpp.server/Resource 
2023.01.16 19:33:24 TRACE [socket_c2s_ssl-thread-2]: org.jivesoftware.openfire.plugin.IQAgentInformationHandler - Perform disco#info request on discord.my.xmpp.server on behalf of user@my.xmpp.server/Resource 
2023.01.16 19:33:24 TRACE [socket_c2s_ssl-thread-2]: org.jivesoftware.openfire.plugin.IQAgentInformationHandler - Perform disco#info request on telegram.my.xmpp.server on behalf of user@my.xmpp.server/Resource 
2023.01.16 19:33:24 TRACE [socket_c2s_ssl-thread-2]: org.jivesoftware.openfire.plugin.IQAgentInformationHandler - Perform disco#info request on skype.my.xmpp.server on behalf of user@my.xmpp.server/Resource 
2023.01.16 19:33:24 TRACE [socket_c2s_ssl-thread-2]: org.jivesoftware.openfire.plugin.IQAgentInformationHandler - Perform disco#info request on icq.my.xmpp.server on behalf of user@my.xmpp.server/Resource 
2023.01.16 19:33:24 TRACE [socket_c2s_ssl-thread-2]: org.jivesoftware.openfire.plugin.IQAgentInformationHandler - Perform disco#items request on my.xmpp.server on behalf of user@my.xmpp.server/Resource 
2023.01.16 19:33:24 TRACE [socket_c2s_ssl-thread-2]: org.jivesoftware.openfire.plugin.IQAgentInformationHandler - Find agents of my.xmpp.server for user@my.xmpp.server/Resource 
2023.01.16 19:33:24 TRACE [socket_c2s_ssl-thread-2]: org.jivesoftware.openfire.plugin.IQAgentInformationHandler - Processing Agent Information request from user@my.xmpp.server/Resource
1 Like
#22

The agentinfo plugin had a problem with discovering information about external components. I’ve logged that issue here. There is now a new snapshot release of the plugin available in which this problem should be fixed.

This should resolve the issue with the Spectrum transports.

The issue with search is probably not fixed by this. I think that boils down to an incompatibility in our search plugin.

The browse plugin likely has the same problem. Let’s verify that the fix for the agentinfo plugin is OK, then we can apply the same fix.

#23

@guus It’s working! :smiley:
Thanks a lot!!

#24

I now applied the same change to the jabber browsing plugin. A snapshot should be available by the time I finish writing this text. I suspect that there are other issues with these plugins.

For one: they do not generate answer for the ‘agents’ themselves, only for the root Openfire domain. When a client queries the root domain (Openfire), the plugin will answer as expected. However, when the clients query a sub-domain (eg: spectrum) directly, then that component is unlikely to understand the request, and will error out. There might be ways around this, but that’s going to be time-consuming.

#25

Sounds like a tricky one. It’s working like it should for me, all running on the same machine. I can register and deregister and everything seems to be working just fine.

1 Like
#26

Well, that’s good to hear. I can live with a couple of theoretical issues if in practice, you’re not running into them. :smiley: