Differences

This shows you the differences between two versions of the page.

--- wiki:advanced:x2gobroker:start [2013/03/28 10:11]
sunweaver [How do I use an X2Go Session Broker with X2Go Client]
+++ wiki:advanced:x2gobroker:start [2015/04/23 03:36] (current)
ionic Add some whitespace.
@@ Line 3: / Line 3: @@
 //Provided by Oleksandr Shneyder, edited by Mike Gabriel//
-===== What is an X2Go Session Broker =====
+===== What is an X2Go Session Broker? =====
 Most of you have already used X2Go Client in standalone mode. X2Go Client in standalone mode allows to be configured by the user himself. Normally, the user creates a set of session profiles that allows the user to work remotely on one or more X2Go Servers. See the documentation that explains [[doc:usage:x2goclient|the usage of X2Go Client]].
@@ Line 21: / Line 21: @@
 </code>
-===== How do I use an X2Go Session Broker with X2Go Client =====
+===== How do I use an X2Go Session Broker with X2Go Client? =====
 If you have access to an X2Go Session Broker, you can launch X2Go Client in broker mode. There are several command line options to configure X2Go Client's broker mode
-  * ''<nowiki>--broker-name=<name></nowiki>'': Name of broker to display in X2Go client. This parameter is optional.
+  * ''<nowiki>--broker-name=<name></nowiki>'': Sets the broker name to display in X2Go Client. This parameter is optional.
-  * ''<nowiki>--broker-url=<protocol>://[username@]<host>[:port]/path</nowiki>'': URL of session broker. Protocol is either of "http", "https" or "ssh". You can specify a username in URL. In this case it will be pasted into authorization dialog of X2Go Client. URL examples are:
+  * ''<nowiki>--broker-url=<protocol>://[username@]<host>[:port]/path</nowiki>'': Sets the URL of the session broker. "protocol" must be one of "http", "https" or "ssh". If "username@" is provided, it will be pasted into the authorization dialog of X2Go Client. URL examples are:
     * ''<nowiki>--broker-url=https://x2gobroker.org/cgi-bin/x2gobroker.cgi</nowiki>''
     * ''<nowiki>--broker-url=ssh://user@x2gobroker.org:22/usr/lib/x2go/x2gobroker.pl</nowiki>''
-  * ''<nowiki>--broker-ssh-key=<path to key></nowiki>'': Path to SSH key to use for authorization against SSH broker. This parameter is only valid with SSH brokers.
+  * ''<nowiki>--broker-ssh-key=<path to key></nowiki>'': Sets the path to an SSH key to use for authentication against an SSH session broker. The client's behavior is undefined if this flag is used for non-SSH session brokers.
-  * ''<nowiki>--broker-autologin</nowiki>'': Use default SSH key or SSH agent for authorization against session broker. This parameter is only valid with SSH brokers.
+  * ''<nowiki>--broker-autologin</nowiki>'': Enables the use of the default SSH key or SSH agent for authentication against an SSH session broker. The client's behavior is undefined if this flag is used for non-SSH session brokers.
-  * ''<nowiki>--broker-noauth</nowiki>'': Do not ask for user credentials during broker authorization. This can be useful if you are using an HTTP(S) broker without authentication.\\ If you run an HTTP(S) server without authentication, but with user-specific profiles, then put the username into the broker URL (see above). The username then will be taken from the broker URL and be sent to the session broker. This option is only valid with HTTP(S) brokers.
+  * ''<nowiki>--broker-noauth</nowiki>'': Does not ask for user credentials during session broker authentication. This can be useful if you are using an HTTP(S) session broker without authentication. If you run an HTTP(S) server without authentication, but with user-specific profiles, then put the user name into the broker URL (refer to --broker-url.) The user name then will be extracted from the broker URL and be sent to the session broker. The client's behavior is undefined if this flag is used for non-HTTP(S) session brokers.

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools