When X authorization is enabled, applications fail to start

For Secure Global Desktop to be able to use X authorization, xauth must be installed on every application server.

If xauth is not installed, you must either install it or disable X authorization on the Security properties panel in Array Manager.

Note This disables X security for the entire array.

If the message "Failed to find xauth" displays in the application launch dialog, Secure Global Desktop can't find the xauth binary. By default, Secure Global Desktop searches the following locations for the xauth binary:

• /usr/bin/X11/xauth
• /usr/X/bin/xauth
• /usr/X11R6/bin/xauth
• /usr/bin/X/xauth
• /usr/openwin/bin/xauth

If the xauth binary is in a different location, you must add its location to the /opt/tarantella/var/serverresources/expect/vars.exp login script. Look for the line beginning "set xauthcmds".

Note If the xauth binary is only in one location, you can speed up application launches by removing the unnecessary locations from the vars.exp login script.

When the user starts an application, the Secure Global Desktop X Protocol Engine generates a cookie and stores it in the .Xauthority file in the user's home directory on the application server. The cookie is used to validate whether or not the user has permission to connect to the X display.

If the user does not have a home directory, the cookie cannot be stored in the user's .Xauthority file and so the user cannot be validated.

You can either:

1. Create a UNIX account for the user on the application server;
2. Disable X authorization on the Security properties panel in Array Manager; or
3. Edit the launch script so that the cookie is stored in a temporary directory.

The launch script you need to edit is /opt/tarantella/var/serverresources/expect/procs.exp.
Change the following line:
execute "[lindex $xauthcmds $i] add $XDISPLAY . $xauthcookie\n"
to something like:
execute "[lindex $xauthcmds $i] -f /tmp/.xauth$username add $XDISPLAY . $xauthcookie\n"