All,
Having read Brad's write-up on the "Point and Shoot VDI" (http://blogs.sun.com/ThinkThin/entry/point_and_shoot_vdi1
), I thought I'd give it a shot. I'm running into issues and I'm not
sure if it's something on my end or something else. In the script
where we use the smartcard as an identifier, the code calls a utuser -
o and greps for the $SUN_SUNRAY_TOKEN to determine what to do:
REG_OTHER=`/opt/SUNWut/sbin/utuser -o | grep $SUN_SUNRAY_TOKEN | awk -
F, '{print $5;}'
When I run utuser -o I get output like:
[EMAIL PROTECTED]:~# utuser -o
MicroPayflex.50020bf600130100,,0,User 1,saturn
OpenPlatform.4090009c247d8f040a17,,0,User 2,
Payflex.50060e9900130100,,0,User 3,
...
and when I examine SUN_SUNRAY_TOKEN for User 1 I see user.
1210550098-7053. Digging deeper a call to utuser -p user.
1210550098-7053 shows that it's considered a "Logical Token" and the
utuser -o only displays the physical token. Clearly a mismatch is
occurring. The script looks at REG_OTHER for a non-null response,
make an additional check, and then fires up uttsc. Obviously I never
make it passed the check on REG_OTHER. My question is there something
I need to do to get these to match, or is it a bug in the script?
Thanks,
Jason.
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
