Ooops, no root ssh and no GUI console
By dragonfly on Nov 23, 2006
Since by default the root user of the OS is used to administer SGD, the way around this is to create another user, and add them to the 'global' group. The easiest way to do that is through the GUI interface, but since I already ruled that out, here are some CLI commands to get the job done. Login via ssh using a non-root user, then su to root in order to run the commands.
First, create a Solaris user. In this case, I used 'sgdadmin' for this task, created as follows, although don't feel obligated to use my method:
useradd -c "SGD Admin" -d /export/home/sgdadmin -m sgdadmin
And now to the SGD configuration, via CLI commands. The first line adds the Solaris user 'sgdadmin' to SGD as a person object, the second adds the new person object to the 'global' group, thus allowing it to administer SGD.
/opt/tarantella/bin/tarantella object new_person --name ".../_ens/o=organization/cn=sgdadmin" --surname none --user sgdadmin
/opt/tarantella/bin/tarantella role add_member --role global --member ".../_ens/o=organization/cn=sgdadmin"
The tricky part of this is the _ens format for SGD objects, used to identify the new person object. These commands are based on using the default installation directory for SGD, so modify them accordingly if you have installed SGD in a location other than the default of /opt/tarantella.
As long as those commands executed without error, you should now be able to login to the SGD GUI as 'sgdadmin' and get access to the Configuration Wizard and Object Manager, regardless of whether you are on the SGD server or not.