Tigase XMPP Server Board

Installation and maintenance: RE: Tigase 7.1 & Message Archiving 1.2 published to maven

Sun, 02/19/2017 - 15:22

We found that maybe we're using the obsolete maven repository.

We manage to find MA 1.2 here:
http://maven-repo.tigase.org/repository/release/tigase/tigase-message-archiving/

And Server 7.1 here:
http://maven-repo.tigase.org/repository/release/tigase/tigase-server/

Thanks in advance and sorry for the spam,
Mauricio Giacomello.

Categories: Tigase Forums

Installation and maintenance: Tigase 7.1 & Message Archiving 1.2 published to maven

Sun, 02/19/2017 - 15:17

Hi folks,

here in our project we build a customized version of tigase that is able to communicate with a few other products and we manage this dependency with your maven repository. We're excited with the release of 7.1 & MA 1.2 so we decided to go ahead and upgrade. However, we found that both versions were not published to the maven repository.
http://maven.tigase.org/tigase/tigase-server/ -> Missing 7.1
http://maven.tigase.org/tigase/tigase-message-archiving/ -> Missing 1.2

Would it be possible to publish them?

Thanks in advance,
Mauricio Giacomello

Categories: Tigase Forums

Installation and maintenance: Tigase 7.1.0 LDAP Authentication Problem

Sun, 02/19/2017 - 12:28

Hi, i just updated to the new tigase 7.1.0 release and I have some troubles getting LDAP authentication to work. I use the same config files as with 7.0.4.
Some clients work fine (psi, jitsi (debian + android), jtalk) but others wont authenticate (conversations (android), movim).

Here is the error log message I get when I try to connect to the server:

2017-02-19 21:10:12.014 [urn:ietf:params:xml:ns:xmpp-sasl Queue Worker 4] ScramCallbackHandler.handleSaltedPasswordCallbackCallback() WARNING: Can't retrieve user password.
tigase.db.TigaseDBException: Not available
at tigase.db.ldap.LdapAuthProvider.getPassword(LdapAuthProvider.java:294)
at tigase.db.AuthRepositoryMDImpl.getPassword(AuthRepositoryMDImpl.java:280)
at tigase.auth.impl.ScramCallbackHandler.handleSaltedPasswordCallbackCallback(ScramCallbackHandler.java:144)
at tigase.auth.impl.ScramCallbackHandler.handleCallback(ScramCallbackHandler.java:77)
at tigase.auth.impl.ScramCallbackHandler.handle(ScramCallbackHandler.java:48)
at tigase.auth.mechanisms.AbstractSasl.handleCallbacks(AbstractSasl.java:52)
at tigase.auth.mechanisms.AbstractSaslSCRAM.processClientFirstMessage(AbstractSaslSCRAM.java:209)
at tigase.auth.mechanisms.AbstractSaslSCRAM.evaluateResponse(AbstractSaslSCRAM.java:151)
at tigase.xmpp.impl.SaslAuth.process(SaslAuth.java:277)
at tigase.server.xmppsession.SessionManager$ProcessorWorkerThread.process(SessionManager.java:2562)
at tigase.util.WorkerThread.run(WorkerThread.java:128)

Here is my tigase ldap auth + user db configuration:

  1. MySQL Database Configuration
    --user-db=mysql
    --user-db-uri=jdbc:mysql://localhost:3306/tigasedatabase?user=tigaseuser&password=pass&useUnicode=true&characterEncoding=UTF-8&autoCreateUser=true
  1. LDAP
    --auth-db=tigase.db.ldap.LdapAuthProvider
    --auth-db-uri=ldaps://ldap.domain.com:636
    basic-conf/auth-repo-params/user-dn-pattern=uid=%1$s,ou=Users,dc=domain,dc=com
    basic-conf/auth-repo-params/sasl-mechs=PLAIN,DIGEST-MD5,CRAM-MD5
    basic-conf/auth-repo-params/non-sasl-mechs=password,digest

Maybe this has to do something with the auth mechanism used by movim and conversations? If you need an test account please let me know!

Thanks in advance,
Ronald Chuck

Categories: Tigase Forums

Installation and maintenance: Wrong Pubsub Database Schema in 7.1.0 Database Install Script

Sun, 02/19/2017 - 12:15

Hi,

the db-create-* scripts use pubsub v3.0.0 schema but tigase 7.1.0 requires v3.2.0.

Kind regards,
Ronald Chuck

Categories: Tigase Forums

API and development: RE: Problem with kicking occupant

Fri, 02/17/2017 - 08:01

I just check the workflow and it works for me! Admin user sends kick IQ:
<iq type="set" to="kick_test@muc.tigase.org" id="afa9a"> <query xmlns="http://jabber.org/protocol/muc#admin"> <item nick="wojtek" role="none"> <reason>spam</reason> </item> </query> </iq> and receives IQ response and presences about user leaving:
<iq from="kick_test@muc.tigase.org" type="result" id="afa9a" to="wojtek@tigase.org/resource"/> <presence from="kick_test@muc.tigase.org/wojtek" type="unavailable" to="wojtek@tigase.org/resource"> <x xmlns="http://jabber.org/protocol/muc#user"> <item affiliation="none" nick="wojtek" role="none"> <reason>spam</reason> </item> <status code="307"/> </x> </presence> <presence from="kick_test@muc.tigase.org/wojtek" type="unavailable" to="wojtek@tigase.org/resource"> <x xmlns="http://jabber.org/protocol/muc#user"> <item affiliation="none" nick="wojtek" role="none" jid="wojciech.kapcia@tigase.org/resource"/> </x> </presence>

And user got correctly removed from the room.

With the limited information that you provide it's hard to troubleshoot your issue! Verify diligently:
  • affiliations of the users;
  • permissions;
In addition:
  • have you made any changes to Tigase Server/MUC code?
  • have you changed room configuration?
  • you could enable debug for muc component --debug=muc and investigate logs.
Categories: Tigase Forums

API and development: RE: Problem with kicking occupant

Wed, 02/15/2017 - 07:15

Vlad Buryj wrote:

1. yes I have affiliation owner
2. yes I use correct addresses
3. for from I use fullJid

[[> <iq from='FullJid'

id='kick1'
to='BareJid'
type='set'>
<query xmlns='http://jabber.org/protocol/muc#admin'>
<item nick='pistol' role='none'>
<reason>Avaunt, you cullion!</reason>
</item>
</query>
</iq>]]

Categories: Tigase Forums

API and development: RE: Problem with kicking occupant

Wed, 02/15/2017 - 07:15

1. yes I have affiliation owner
2. yes I use correct addresses
3. for from I use fullJid

<iq from='FullJid'
id='kick1'
to='BareJid'
type='set'>
<query xmlns='http://jabber.org/protocol/muc#admin'>
<item nick='pistol' role='none'>
<reason>Avaunt, you cullion!</reason>
</item>
</query>
</iq>

Categories: Tigase Forums

API and development: RE: 7.1.0:urn:xmpp:delay

Wed, 02/15/2017 - 06:25

Thanks!

Categories: Tigase Forums

API and development: RE: 7.1.0:urn:xmpp:delay

Wed, 02/15/2017 - 06:19

jiafu wu wrote:

I would like to show the message in the chat room time, but 7.1.0 version of the message returned without <delay /> tag

Such messages are received when the user is online, thus you simply display time when the message was received (it's the same time).

Categories: Tigase Forums

Installation and maintenance: RE: Private Certificate

Wed, 02/15/2017 - 06:17

Alex Kobzar wrote:

So, that is my question.
I have a cert from comodo in 7b format.
So, i convert it to pem

openssl pkcs7 -in certificate_file.p7b -print_certs -out cert.pem
after this put it in to certs dir and restart tigase but have error:

[...]

Make sure you have everything in the file - your certificate, private key (and if needed - intermediate certificates) - check Subject and Issued fields of the file (certificates) and verify that used JVM version have root CA in the trusted CA store.

Categories: Tigase Forums

Installation and maintenance: RE: Private Certificate

Tue, 02/14/2017 - 23:05

So, that is my question.
I have a cert from comodo in 7b format.
So, i convert it to pem

openssl pkcs7 -in certificate_file.p7b -print_certs -out cert.pem
after this put it in to certs dir and restart tigase but have error:

2017-02-15 07:02:08.851 [main] SSLContextContainer.init() WARNING: Cannot load certficate from file: certs/cert.pem
java.lang.RuntimeException: Can't find root certificate in chain!
at tigase.cert.CertificateUtil.sort(CertificateUtil.java:586)
at tigase.cert.CertificateUtil.sort(CertificateUtil.java:572)
at tigase.io.SSLContextContainer.addCertificateEntry(SSLContextContainer.java:167)
at tigase.io.SSLContextContainer.init(SSLContextContainer.java:394)
at tigase.io.TLSUtil.configureSSLContext(TLSUtil.java:86)
at tigase.conf.ConfiguratorAbstract.setProperties(ConfiguratorAbstract.java:772)
at tigase.conf.ConfiguratorAbstract.setup(ConfiguratorAbstract.java:519)
at tigase.conf.ConfiguratorAbstract.componentAdded(ConfiguratorAbstract.java:152)
at tigase.conf.Configurator.componentAdded(Configurator.java:50)
at tigase.conf.Configurator.componentAdded(Configurator.java:33)
at tigase.server.AbstractComponentRegistrator.addComponent(AbstractComponentRegistrator.java:116)
at tigase.server.MessageRouter.addRegistrator(MessageRouter.java:138)
at tigase.server.MessageRouter.setConfig(MessageRouter.java:644)
at tigase.server.XMPPServer.start(XMPPServer.java:142)
at tigase.server.XMPPServer.main(XMPPServer.java:112)

Categories: Tigase Forums

API and development: RE: 7.1.0:urn:xmpp:delay

Tue, 02/14/2017 - 17:00

I would like to show the message in the chat room time, but 7.1.0 version of the message returned without <delay /> tag

Categories: Tigase Forums

API and development: RE: 7.1.0:urn:xmpp:delay

Tue, 02/14/2017 - 08:33

It was removd in tigase-muc commit:92060a9b3f3395d375e19583842253799e36a874 as it wasn't a correct specification implementation (it should be included only in messages returned from archive).

What's the use-case for the <delay/> tag in typical messages?

(#4109)

Categories: Tigase Forums

API and development: 7.1.0:urn:xmpp:delay

Mon, 02/13/2017 - 19:47

7.0.4 before the return of the message in the delay :<message xmlns="jabber:client" type="groupchat" from="/a" to="a@a51-pc/Spark 2.8.2.934" id="PgPkT-193"><body>@###</body><delay stamp="2017-02-13T08:49:43Z" xmlns="urn:xmpp:delay"/></message>
7.1.0 version of the return message did not delay :<message from="/a" type="groupchat" id="6WA3O-277" to="a@a51-pc/Spark 2.8.2.934" xmlns="jabber:client"><body>@###</body></message>

I would like to return in the 7.1.0 version:
<delay stamp="2017-02-13T08:49:43Z" xmlns="urn:xmpp:delay"/>

What should I do?

Categories: Tigase Forums

API and development: RE: MUC Group Avatar

Sun, 02/12/2017 - 22:54

Thanks for your reply, we will check.

Categories: Tigase Forums

Installation and maintenance: RE: Private Certificate

Fri, 02/10/2017 - 14:57

Alex Kobzar wrote:

the cert must be only in pem format ?

Yes, Tigase support certificates only in PEM format, but you can convert to it from (almost?) any format.

Categories: Tigase Forums

Installation and maintenance: RE: Private Certificate

Fri, 02/10/2017 - 07:24

the cert must be only in pem format ?

Categories: Tigase Forums

API and development: RE: tigase server(v7.1.0) and client(v3.0.0) incompatibility

Thu, 02/09/2017 - 17:39

Thank you very much Andrzej! The suggested property did the trick. We are going to update the android client to use the latest stable v3.1.5 tigase-client release, but in the meantime, this flag will help us maintain backward compatibility.

Categories: Tigase Forums

API and development: RE: tigase server(v7.1.0) and client(v3.0.0) incompatibility

Thu, 02/09/2017 - 12:28

I think I may know what is happening here. If I'm correct in rfcCompatible mode Jaxmpp uses WebSocket connection as specified in RFC. However before version 3.1.0 of Jaxmpp it was sending WebSocket frames with unmasked data and server was accepting it. In Tigase XMPP Server 7.1.0 we started rejecting connections from WebSocket based clients which are sending unmasked data which may lead to such incompatibility. (only if Jaxmpp-J2SE is used).

This change #4068 was introduced during development of Tigase XMPP Server 7.1.0 and Jaxmpp 3.1.0 to make them fully compatible with RFC specifying WebSocket and XMPP-over-WebSocket as they require that server must drop connection from client if it is sending unmasked data.

There are 2 possible solutions:
  • upgrade to Jaxmpp 3.1.x series (current stable version of Jaxmpp)
  • force server to accept unmasked frames from client by adding following line to etc/init.properties file:
    --ws-allow-unmasked-frames=true
Categories: Tigase Forums

Installation and maintenance: RE: Private Certificate

Thu, 02/09/2017 - 07:02

Alex Kobzar wrote:

Couldn't understand how to use my own certificate with tigase?
I was:
Stop server
clean certs directory
put my file.pem

By the rule of thumb you should place your certificate in the file which name matches the vhost (so for example as seen below: domain.com.pem)

add to init.properties next lines
--ssl-container-class=tigase.io.SSLContextContainer
basic-conf/virt-hosts-cert-*.domain.com=/etc/tigase/certs/file.pem

Unless needed you should not use manual configuration.

start server.
But after this actions tigase generate himself cert with domain.com.pem and use it.
What's my mistake?
tig v.7.1.0

Looking at complete logs from the startup (adding cert to debugging configuration will help) will give you more information.

Please note, that you need to provide your certificate and full certification chain and your private key within pem file.

Categories: Tigase Forums

Pages

Get in touch

We provide software products, consulting and custom development services

Tigase, Inc.
100 Pine Street, Suite 1250
San Francisco, CA 94111, USA
Phone: (415) 315 9771

Follow us on:

Twitter

Back to Top