Hi Anders,

Thank you for your support. I have done all the instructions that you said but it doesn't work. The The DEBUG options were already enabled and I have seen the client computer IP on the public key on a log file.
Maybe I must to explain how is our network configuration.

- Client computers don't have access to the servers. Client computers only have access to the broker server.
- Broker server have access to x2go servers and client computers.
- x2go servers only have access to broker server (this is a private network).

Thanks,

A 2013-06-03 14:47, Anders Bruun Olsen escrigué:

Hi,

 

I have read about problems with the AuthorizedKeysFile2 option. My servers just use AuthorizedKeysFile to set two paths:

 

AuthorizedKeysFile %h/.ssh/authorized_keys %h/.x2go/authorized_keys

 

Have you tried running x2gobroker-daemon in debug mode and looking in the logfile, to see if anything useful gets logged?

Set X2GOBROKER_DEBUG=1 in /etc/default/x2gobroker-daemon

 

Also, I assume that you have the requisite ssh-keys setup, so your broker can login to your terminalservers? You need to have run x2gobroker-keygen on the broker, and x2gobroker-pubkeyauthorizer -t http://BROKER:8080/pubkeys on your x2go servers. Followed by su'ing to the x2gobroker on your broker and then ssh'ing to your x2go servers and accepting the host keys.

 

2013/6/3 Juan Carlos Corchado <jcorchado@tsc.upc.edu>

Hi,

Thank you for the support. I have included the option "broker-session-autologin=true" on x2gobroker-sessionprofiles.conf but when I choose the KDE or GNOME appears "connection refused (or timed out)". Some options that I set on /etc/x2go/x2gobroker.conf are:

check-credentials = true
default-session-autologin=true

And I already include on /etc/ssh/sshd_config this line:

AuthorizedKeysFile2    %h/.x2go/authorized_keys.

I noticed that when ocurs this error I need to restart the process "x2gobroker-daemon" because is stopped.

Thanks,

 

A 2013-06-03 10:57, Anders Bruun Olsen escrigué:

Hi Juan,

 

That was one of my first questions as well :)

You will need to configure auto-login, which means that your clients will only need to authenticate to the broker. The broker will then place a temporary public ssh-key on the chosen x2goserver and give the corresponding private key to the client, allowing the client to login to that server, without a password. If I remember correctly, you just need to enable it in /etc/x2go/broker/x2gobroker-sessionprofiles.conf, by setting broker-session-autologin=true for the profiles you wish to have autologin on.

2013/6/3 Juan Carlos Corchado <jcorchado@tsc.upc.edu>

Hi all,

The x2go-broker configuration is working correctly but when I try the command x2goclient --broker-url=http://server:8080/plain/inifile/ and set the name and password appears another window to select KDE or GNOME (my configuration). When I choose one of them I have to set again the user and password. It's possible to put it just once?

Thanks,

 

_______________________________________________
X2Go-User mailing list
X2Go-User@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/x2go-user

 

--
Anders Bruun Olsen
It-ansvarlig
Det Danske Sprog- og Litteraturselskab
(Society for Danish Language and Literature)

 

 

 

--
Anders Bruun Olsen
It-ansvarlig
Det Danske Sprog- og Litteraturselskab
(Society for Danish Language and Literature)