Project

General

Profile

Bug #5525

Unable to establish S2S connection

Added by Andrzej Wójcik IoT 1 CloudTigaseTeam almost 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Database:
n/a
Applicable version:
git/master
Source Code Disclaimer:

Description

With latest version 7.2.0-SNAPSHOT it is not possible to establish S2S connection, as Tigase XMPP Server returns invalid-namespace error.

Associated revisions

Revision 7340cdb3 (diff)
Added by Andrzej Wójcik IoT 1 CloudTigaseTeam almost 2 years ago

#5525: fixed S2S connectivity issue, invalid-namespace error being returned during connection establishment

History

#1 Updated by Andrzej Wójcik IoT 1 CloudTigaseTeam almost 2 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

During porting of S2SConnectionManager to Tigase Kernel, PacketChecker was moved from filters map to processors which caused this issue as it forced connection establishment packets namespace to be jabber:client or jabber:server@, while others are allowed at this point as well (ie. XMLNS related to @starttls@). I moved @PacketChecker back to filters which solved this issue.

Also available in: Atom PDF