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:32] sunweaver |
wiki:advanced:x2gobroker:howitworks [2013/03/28 10:38] sunweaver [Providing Auto-Login via SSH Keys] |
||
---|---|---|---|
Line 138: | 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 162: | 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 196: | 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 |