European Grid Infrastructure

towards a sustainable infrastructure

Jump to Menu

Jabber HOWTO

Experimental server

Because of problems with the orginal server, we setup a new experimental instance. After some time of pilot traffic it will replace jabber.egi.eu.

Client settings

Configuration of various clients slightly differs, however, the following information has to be entered:

Protocol XMPP (Jabber)
Username your EGI SSO username
Password your EGI SSO password
Server (Domain) indico.egi.eu
Port 5222

In order to integrate with EGI SSO, the server must accept plain-text passwords. In order to keep it safe, the connection is encrypted with SSL.

Clients may require switching on options like Require encryption and Allow plaintext password. However, Allow plaintext over unencrypted streams is dangerous and it should not be switched on.

The accounts exists on the server by the integration with EGI SSO, therefore do not let the client create the account (it would fail either)

Chat rooms

Users are allowed to create either volatile or persistent chat rooms on the server. However, access to those chat rooms is restricted to the users of jabbber.egi.eu only (ie. the chat server is not accessible for external XMPP users).

In order to setup a chat room, provide the following information to your client (using its Add chat or similar command):

Account your_username@jabber.egi.eu
Room the chatroom name
Server conference.localhost
Handle your nickname in the chatroom
Password shared room password

A particular trick is the weird conference.localhost server name. It reflects the local-only setup within the jabber server.

The password is required only if access restriction to the room is applied.

Upon creation of the room a dozen of other options can be specified. The most important one is making the room persistent (survive server restarts) or volatile. Otherwise use your common sense.

Original server

The old server is buggy, known to hang connection from time to time. Consider using the new one above.

Client settings

Configuration of various clients slightly differs, however, the following information has to be entered:

Protocol XMPP (Jabber)
Username your EGI SSO username
Password your EGI SSO password
Server (Domain) jabber.egi.eu
Port 5222 or 5223

In order to integrate with EGI SSO, the server must accept plain-text passwords. In order to keep it safe, the connection is encrypted with SSL. The SSL-enforced server runs on both port 5222 and 5223 (some clients may not be able to connect to 5222 using SSL).

Clients may require switching on options like Force old (port 5223) SSL and Allow plaintext password. However, Allow plaintext over unencrypted streams is dangerous and it should not be switched on.

The accounts exists on the server by the integration with EGI SSO, therefore do not let the client create the account (it would fail either)

Chat rooms

Users of jabber.egi.eu are allowed to create either volatile or persistent chat rooms on the server. However, access to those chat rooms is restricted to the users of jabbber.egi.eu only (ie. the chat server is not accessible for external XMPP users).

In order to setup a chat room, provide the following information to your client (using its Add chat or similar command):

Account your_username@jabber.egi.eu
Room the chatroom name
Server conference
Handle your nickname in the chatroom
Password shared room password

A particular trick is the weird conference server name. It reflects the local-only setup within the jabber server.

The password is required only if access restriction to the room is applied.

Upon creation of the room a dozen of other options can be specified. The most important one is making the room persistent (survive server restarts) or volatile. Otherwise use your common sense.