Friday Jun 26, 2009

Using different Kiosk Sessions for different tokens

Original Sun Ray Kiosk Mode or its predecessor CAM only allowed one Kiosk configuration that applied to all kiosk sessions on a server. Since SRSS 4.1 there is a little known feature that allows adding additional kiosk configurations and selecting one them based on the token.

Unfortunately configuring this feature currently requires using the utkiosk and utkioskoverride tools on the command line. This probably is the main reason why add-on solutions to do the same, like Daniel Cifuentes's Meta-Kiosk are still popular.

For those not afraid of the command line, here is a short how-to

  1. Create a kiosk session configuration.

    You first need to create a file (named UserSession.conf here, but you can freely choose a name) containing your kiosk session configuration. Of course you can simply create it as a text file, after reading the session.conf(4) man page. But if you prefer to use the SRSS Web Admin GUI for this step, you can do it as follows:

    • Configure the session settings on the Edit Kiosk Session page
    • If you are using the JDS desktop session, add the applications you want to see in the menu.
    • Save your changes
    • Get a root shell on one of the servers and use it to save the configuration to a file:
      # cd  # Make sure your are in a reasonable directory to store your configurations
      # PATH=${PATH}:/opt/SUNWut/sbin    # Save yourself (and me) some typing
      # utkiosk -e session -s > UserSession.conf
      
    • If you have configured applications, also save the application list to a file:
      # utkiosk -e session -a > UserSessionApps.list
      

  2. Store your kiosk session configuration in the Sun Ray data store.

    You now need to store your configuration in SRDS, so it can be used for Sun Ray kiosk sessions. You can store each configuration under a name you choose. This example will use UserSession. Use a name that starts with a capital letter - all-lowercase names are reserved.

    If you don't need an application list, you can simply upload your UserSession.conf file like this:

    # utkiosk -i UserSession -f UserSession.conf
    

    If you did create an application list, the command looks like this:

    # utkiosk -i UserSession -f UserSession.conf -A UserSessionApps.list
    

  3. Configure individual tokens to use this kiosk session configuration.

    You now need to assign this configuration to selected tokens. I'll show this here for the imaginary CleverCard.0123456789 card token. You can assign kiosk setting to selected DTUs (when used without a smart card) in the same way.

    • In order to apply special kiosk setting to the token, it needs to be registered (even if you don't use a "registered" access policy). If the token isn't registered yet, you can do this now without leaving the command line:
      # utuser -a "CleverCard.0123456789,localhost,0,John Doe,"
      
    • Now you can assign the UserSession configuration to the token:
      # utkioskoverride -r CleverCard.0123456789 -s kiosk -c UserSession 
      
      Note: This will enable Kiosk Mode for this token, even if it isn't enabled globally.

    • If you have stored multiple session configurations, you can view them using:
      # utkiosk -l
      session
      UserSession
      
      The session configuration is the default kiosk configuration, which is used for all kiosk session that haven't been assigned an override.
About

Musings about my work in the (virtual) desktop space and whatever else moves me.

Keep on your desktop at all times.

Disclaimer: The statements and opinions expressed here are my own and do not necessarily reflect those of Oracle

Search

Archives
« July 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  
       
Today