Hello Jason,


  The code you quote explains a common trick to fetch the DTU identifier. 

I would more clearly call this variable SUN_SGD_DTULOCATION instead of 

SUN_SGD_CLIENTNAME, though. Because the "client name" might be an actual 

person's name from the token's attributes (i.e. smart-card). And depending 

on your applications, this may have some certain value in itself - along 

with the "location" or even overriding it.


  This logic typically goes into session startup scripts, that is - any 

step which executes before your client applications start. This may be 

general X11 server startup for all users, or the specific Kiosk Config's 

routines.


  General X11 injection locations were well described here, IIRC:

http://blogs.sun.com/ThinkThin/entry/how_to_lock_registered_smart

http://blogs.sun.com/ThinkThin/resource/0005.utcard_check


  To me, the trick would be passing the SUN_SGD_CLIENTNAME to the browser 

and on to the web-applications launched from it. I guess this value can be 

set in the browser's launch URL as a GET parameter, but I'm somewhat vague 

about the next passing-on's - from SGD to its clients launch parameters.


  Beside, if your users hotdesk (this now includes logging into their SGD

accounts from a different Sun Ray or perhaps any computer in general), the 

already-started Windows session would keep running on with the first set 

"location" value.


  So maybe using some common datastore between Sun Ray/SGD servers and 

Windows apps, like LDAP or AD or a database or a fileserver, and scripting 

up some wrappers on both sides to capture the event of logging-in or 

hotdesking (ask the list how, I'm also curious), would better serve to 

pass valid values between systems.


  Here's my guess worth 2 cents ;)


//Jim



Thursday, August 20, 2009, 9:18:25 PM, you wrote:


>

Team,


I have a health care customer that's got about 500 Sun Rays and they've just implemented SGD to support about 500 concurrent users.  The Sun Rays use a Firefox browser hosted on a kiosk-mode Java Desktop (JD3) implemented according to Brad's posting here: http://blogs.sun.com/ThinkThin/entry/kiosk_mode_browser.  Our customer requested an enhancement from the SGD team to allow them to grab the Sun Ray desktop "Location" value from the SR Datastore and pass this to the SGD client  ... this would then be passed to the Windows Terminal Services session when its opened.  The customers HIS system, Eclipsys SCM, requires this TS Client Name name to be maintained in its own datastore, otherwise the session is rejected.  The SGD team has given us the fix and some of the details of how to implement, including new client bits, but I'm not quite sure how to best set this variable for each kiosk session (each kiosk user); SUN_SGD_CLIENTNAME.


I believe this is the logic I need - but where do I put it so this value gets set when a session starts??

MYDISP=`echo $DISPLAY | awk -F: '{print $2}' | awk -F. '{print $1}'`

MYMAC=`grep TERMINAL /tmp/SUNWut/config/dispinfo/$MYDISP | awk -F. '{print $2}'`

# grab the value from Location field for this specific MAC

SUN_SGD_CLIENTNAME=`/opt/SUNWut/sbin/utdesktop -l | grep $MYMAC | awk '{print $2}'`

export SUN_SGD_CLIENTNAME


Should I put this in /etc/profile or some other place where each kiosk user (utku*) can pick this up?  I tried /etc/profile without success, actually, it worked for some users but not the kiosk users - maybe they're using different shells.  Where does SUN_SUNRAY_TOKEN get set?


Thanks! 





-- 

Best regards,

 Jim Klimov                            mailto:[email protected]

_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users

Reply via email to