This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
wiki:advanced:x2gobroker:howitworks [2013/03/28 10:17] sunweaver [Authentication methods against X2Go Session Broker] |
wiki:advanced:x2gobroker:howitworks [2013/03/28 10:38] sunweaver [Providing Auto-Login via SSH Keys] |
||
---|---|---|---|
Line 22: | Line 22: | ||
===== Extra Security: Pre-shared Authentication ID ===== | ===== Extra Security: Pre-shared Authentication ID ===== | ||
- | With both types of broker | + | With both session broker |
The file path to the authentication ID has to be specified as the X2Go Client command line option ''< | The file path to the authentication ID has to be specified as the X2Go Client command line option ''< | ||
+ | |||
+ | The usage of this feature is optional. | ||
===== Don't Check User Data ===== | ===== Don't Check User Data ===== | ||
- | In some setups it can make sense to give access to the X2Go Session Broker without authentication. | + | In some setups it can make sense to give access to the X2Go Session Broker without authentication. |
+ | |||
+ | __Example: | ||
When implementing your own session broker, you can configure the broker not to check the username (and password) at all. This is only possible with HTTP based brokers. | When implementing your own session broker, you can configure the broker not to check the username (and password) at all. This is only possible with HTTP based brokers. | ||
- | With SSH based X2Go Session Broker implementations, | + | With SSH based X2Go Session Broker implementations, |
===== Granting Access to the Broker ===== | ===== Granting Access to the Broker ===== | ||
Line 74: | Line 78: | ||
The only difference occurs in the parameters '' | The only difference occurs in the parameters '' | ||
- | Furthermore, | + | Furthermore, |
=== The session profile option: host === | === The session profile option: host === | ||
Line 81: | Line 85: | ||
In load balancing setups, the best server will be | 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 | + | chosen after selection of a session profile. Once the best server has been detected, it is sent to X2Go Client and X2Go Client |
+ | |||
+ | 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 session profile option: key === | ||
Line 94: | Line 100: | ||
=== The session profile option: usebrokerpass === | === The session profile option: usebrokerpass === | ||
- | The parameter '' | + | The parameter '' |
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. | 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 | + | It is highly |
=== The session profile option: status === | === The session profile option: status === | ||
Line 108: | Line 114: | ||
===== Selecting a Session Profile ===== | ===== Selecting a Session Profile ===== | ||
- | After login to the X2Go Session Broker a list of provided session profiles is shown in X2Go Client. The user can now choose one session profile from this list. The ID of chosen session profile will be sent to the broker and the broker sends the connection data back to X2Go Client. | + | After login to the X2Go Session Broker a list of provided session profiles is shown in X2Go Client. The user can now choose one session profile from this list. The ID of the chosen session profile will be sent to the session |
- | ==== Generic function: | + | ==== Generic function: |
This is a generic example for the " | This is a generic example for the " | ||
Line 132: | Line 138: | ||
If no other data is specified, a new X2Go session will be created. | If no other data is specified, a new X2Go session will be created. | ||
- | The X2Go Session Broker can also send information back to client, that tells the client to resume a suspend session. | + | The X2Go Session Broker can also send information back to X2Go Client, that tells the client to resume a suspend session. |
- | In this case the X2Go Session Broker | + | In the code example below, additionally to the X2Go Server hostname, |
<code perl> | <code perl> | ||
sub selectSession | sub selectSession | ||
Line 156: | Line 162: | ||
==== No Auto-Resuming of Sessions ==== | ==== No Auto-Resuming of Sessions ==== | ||
- | If X2Go Client is running in broker mode, it will not verify if there are existing sessions on X2Go Server. | + | If X2Go Client is running in broker mode, it will not verify if there are existing sessions on the targeted |
- | It is the responsibility of the X2Go Session Broker. The X2Go Broker should also suspend sessions before providing session data to client | + | Checking for running/ |
==== Providing Auto-Login via SSH Keys ==== | ==== Providing Auto-Login via SSH Keys ==== | ||
Line 190: | Line 196: | ||
</ | </ | ||
- | Providing SSH keys can be increase usability | + | Providing SSH keys for X2Go Server sessions |
It is highly recommended to transfer SSH keys only over encrypted channels (HTTPS or SSH broker). | It is highly recommended to transfer SSH keys only over encrypted channels (HTTPS or SSH broker). | ||
- | It is also recommended to transfer | + | It is also recommended to only transfer a temporary |