Tigase.org is the website of the Tigase XMPP/Jabber Server
- Cluster with over 1mln online users.
- 500k online users on a single machine.
- Great at XMPP service sharding.
- Running happily with 10MB of RAM.
- Long list of supported features.
- Scripting support for all major languages.
- All tests results are publicly available.
- Very flexible and extensible API.
- Monitoring via HTTP, SNMP, JMX, XMPP.
If you are interested in the Tigase project and want to participate in any way you can request an account on the website and Jabber server in domain tigase.org. Please use the contact form to request the account and describe your planed involvement in the project. You can report bugs or request new features on the project tracker.
If you are looking for a free, XMPP account offered from the Tigase based service you should check the Tigase.im Website. This is the place where the last development version of the Tigase server is running. Check the website for more details.
For professional services and commercial Tigase products please refer to the company website: www.tigase.com
By default user passwords are stored in plain-text in the Tigase's database. However, there is an easy way to have them encoded in either one of already supported ways or to even add a new encoding algorithm on your own. The reason to store passwords in plain-text format in the database is to make it possible to avoid plain-text password authentication mechanism. At the moment you cannot have hashed passwords in the database and non-plain-text password authentication. On the other hand, the connection between the server and the client is almost always secured by SSL/TLS so maybe the plain-text password authentication method is less of a problem than storing plain-text passwords in the database. Nevertheless, it is simple enough to adjust this in Tigase's database and we will add an option in the Tigase installer to allow you to make the decision at installation time.
Splitting user authentication data from all other XMPP information such as roster, vcards, etc... was almost always possible in Tigase XMPP Server. Possible and quite simple thing to configure. Also it has been always possible and easy to assign a different database for each Tigase component (MUC, PubSub, AMP), for recording the server statistics. Almost every data type or component can store information in a different location, simple and easy to setup through the configuration file.
However it is much less known that it is also possible to have a different database for each virtual domain. This applies to both the user repository and authentication repository. This allows for very interesting configuration such as user database sharding where each shard keeps users for a specific domain, or physically split data based on virtual domain if each domain refers to a different customer or group of people.
How can we do that then?
Tigase STUN server is now available for a public use.
The domain name tigase.org points to the STUN primary IP address. It is implemented as the Tigase component and it is integrated into our XMPP server running for tigase.org address. Feel free to point your software to our address and use it, for free.
Let us know, how it works and if you have any problems or comments.
We have already had quite a few requests and questions regarding access to source code repository and problems with Git.
We are sorry for any problems and delays. They were mainly caused by problems with integration with our Redmine installation and user authorization/authentication mechanisms.
Right now everything seems to be working properly and most of our code repositories have been moved and are working correctly. Please check them out and let us know if you still have any problems.