[X2Go-Commits] page changed: wiki:advanced:x2gobroker:howitworks

[wiki-admin at x2go.org]

A page in your DokuWiki was added or changed. Here are the details:

Date        : 2013/03/28 10:30
Browser     : Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 Iceweasel/18.0.1
IP-Address  : 46.142.186.224
Hostname    : 224-186-142-46.pool.kielnet.net
Old Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:howitworks?rev=1364466175
New Revision: http://wiki.x2go.org/doku.php/wiki:advanced:x2gobroker:howitworks
Edit Summary: [Session Profile Format] 
User        : sunweaver

@@ -76,16 +76,18 @@
  The option keys and values are the same as in X2Go Client's configuration file (''~/.x2goclient/sessions'').
  
  The only difference occurs in the parameters ''host=<hostname>'' and ''key=<keyfile>''. 
  
- Furthermore, there are two parameters that are not supported in the ''sessions'' file, but are only functional when X2Go Client is in broker mode: ''status=<status>'' and ''usebrokerpass={true,false}''.
+ Furthermore, there are two extra parameters that
are not supported in the ''sessions'' file, but have a special functionality when X2Go Client is run in broker mode: ''status={R,S}'' and ''usebrokerpass={true,false}''.
  
  === The session profile option: host ===
  
  The ''host='' parameter is not necessarily a hostname of an X2Go Server. The actual address of the server will be provided after the session profile has been selected by the user. Delaying the provision of the X2Go Server name makes sense in a cases where X2Go Session Broker is used as a [[wiki:advanced:x2gobroker:loadbalancing|load balancer]].
  
  In load balancing setups, the best server will be
- chosen after selection of a session profile. Once the best server has been detected, it is sent to X2Go Client and X2Go Client use the best server's hostname for authentication and session startup. When resuming an X2Go session, the broker will know the server that runs the suspended session and return that one, so that the user can continue his/her earlier session.
+
chosen after selection of a session profile. Once the best server has been detected, it is sent to X2Go Client and X2Go Client uses this best server's hostname for authentication and session startup.
+ 
+ When resuming an X2Go session, the broker will know the server that runs the suspended session and return that one, so that the user can continue his/her earlier session.
  
  === The session profile option: key ===
  
  The ''key='' parameter is simply ignored when returned via an X2Go Session Broker.
@@ -96,13 +98,13 @@
  tried, for example: ''key=will-be-provided-later''.
  
  === The session profile option: usebrokerpass ===
  
- The parameter ''usebrokerpass={true,false}'' is used to denote that requesting the user password for this session is not necessary, but that the X2Go Client should rather use the broker password instead. 
+ The parameter ''usebrokerpass={true,false}'' is used to denote that requesting the user password for this session is not necessary, but that the
X2Go Client should rather use the broker's //username and password// tuple instead. 
  
  This can be useful if the X2Go Session Broker and the X2Go Server use the same authentication server (e.g. same LDAP db) and there is no need to ask the same password twice. 
  
- It is not recommended to use such authentication with an HTTP Broker without SSL encryption.
+ It is highly recommended to only use this feature on HTTPS brokers (i.e. with SSL encryption for the X2Go Client <-> X2Go Session Broker communication) or SSH brokers.
  
  === The session profile option: status ===
  
  The parameter ''status={S,R}'' can be one of two values "S" or "R". It can be used to tell X2Go Client that an instance (or instances) of this session profile are already running or are suspended on the server. 



-- 
This mail was generated by DokuWiki at
http://wiki.x2go.org/