Difference between revisions of "Jabber How To"

From EGIWiki
Jump to: navigation, search
(Created page with "==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. ===Cl...")
 
(moving here info from the main egi.eu website)
Line 30: Line 30:
  
 
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)
 
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
+
 
 +
===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).
 
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):
 
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
+
{| class="wikitable"
Server conference.localhost
+
|-
Handle your nickname in the chatroom
+
|Account
Password shared room password
+
|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.
 
A particular trick is the weird conference.localhost server name. It reflects the local-only setup within the jabber server.
Line 46: Line 60:
  
 
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.
 
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
+
 
 +
==Original server==
  
 
The old server is buggy, known to hang connection from time to time. Consider using the new one above.
 
The old server is buggy, known to hang connection from time to time. Consider using the new one above.
Client settings
+
 
 +
===Client settings===
  
 
Configuration of various clients slightly differs, however, the following information has to be entered:
 
Configuration of various clients slightly differs, however, the following information has to be entered:
Protocol XMPP (Jabber)
+
 
Username your EGI SSO username
+
{| class="wikitable"
Password your EGI SSO password
+
|-
Server (Domain) jabber.egi.eu
+
|Protocol
Port 5222 or 5223
+
|XMPP (Jabber)
 +
|-
 +
|Username  
 +
|your EGI SSO username
 +
|-
 +
|Password
 +
|your EGI SSO username
 +
|-
 +
|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).
 
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).
Line 63: Line 92:
  
 
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)
 
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
+
 
 +
===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).
 
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):
 
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
+
{| class="wikitable"
Handle your nickname in the chatroom
+
|-
Password shared room password
+
|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.
 
A particular trick is the weird conference server name. It reflects the local-only setup within the jabber server.

Revision as of 17:15, 28 June 2016

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 username
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 username
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.