XMPPServer#matchesComponent shouldn't require full-JID match

Description

The implementation of org.jivesoftware.openfire.XMPPServer#matchesComponent will return true for aJID of a local component (eg: conference.example.org), but will return false for a JID of a entity-of-that-domain (eg: myroom@conference.example.org}}. Most, if not all, of its uses assume that the latter would return true.

I believe that this is a problem in how its implementation assumes that org.jivesoftware.openfire.component.InternalComponentManager#hasComponent will evaluate only the domain-part of the JID, while in fact it performs an exact match (which fails if a node- or resource-part is present).

Environment

None

Activity

Show:
Fixed

Details

Assignee

Reporter

Fix versions

Priority

Created December 1, 2021 at 3:29 PM
Updated December 2, 2021 at 2:16 PM
Resolved December 2, 2021 at 2:16 PM

Flag notifications