Hi Jens,
Can you make sure everything is sane with the token to conf assignments?
Here's a little script you can run:
#!/bin/sh
#set -x
UTUSER=/opt/SUNWut/sbin/utuser
UTKIOO=/opt/SUNWut/sbin/utkioskoverride
printf "%-42s %-19s %-20s\n" "TOKEN ID" "OWNER" "KIOSK SESSION NAME"
echo
"----------------------------------------------------------------------------------------"
for i in ` $UTUSER -Ls kiosk | grep kiosk | awk '{print $1}'`;
do
theUser=`$UTUSER -p $i | grep "User Name" | /usr/bin/awk -F= '{print $2}'`
theConfig=`$UTKIOO -r $i | grep SESSION_CONFIG | /usr/bin/awk -F=
'{print $2}'`
printf "%-41s %-20s %-20s\n" "$i" "$theUser" "$theConfig"
done
#end of script
On 7/9/12 11:13 AM, Niki W. Waibel wrote:
Strange. I have a very similar Setup, upgraded as well, but i Do Not See
any issues with token based Kiosk sessions. IIRC, i Set KIOSK_SESSION
var in each of the different .conf Files...
--
Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.
"Dr. Jens Langner" <[email protected]> wrote:
Hi,
we are using "utkioskoverride" extentensively to set self-defined kiosk
sessions based on tokens. Since upgrading from 5.2.5 to 5.3.1 the
sunrays with token that have sessions set with "utkioskoverride -c
<config>" don't work properly anymore. After reinstalling 5.3.1 the
problem remains. Log files show the following entries:
-- cut here --
Jul 4 18:12:29 elly dtlogin[8108]: [ID 976841user.info
<http://user.info>] pam_kiosk:
pam_sm_authenticate: Initiating Kiosk session with user utku0
Jul 4 18:12:30 elly kiosk:initsession[8204]: [ID 702911 user.error]
Error: No KIOSK_SESSION defined for display ':2'
Jul 4 18:12:30 elly kiosk:initsession[8204]: [ID 702911 user.error]
Error: failed to load Session Descriptor
Jul 4 18:12:30 elly dtlogin[8108]: [ID 705508 user.error] pam_kiosk:
pam_sm_open_!
session:
Child process /opt/SUNWkio/lib/initsession failed
with exit code 1
-- cut here --
Setting a global kiosk session via the web management works. However,
wenn binding only a certain token via utkioskoverride, the above error
occur. Did something change in the setup procedure when configuring own
kiosk sessions via:
1) creating a .conf and session files under /etc/opt/SUNWkio
2) loading this .conf file in ldap via "utkiosk -i <name> -f <file.conf>"
3) setting a token to use this session via "utkioskoverride -r <token>
-s kiosk -c <name>
If not, than this might be potentially a bug in 5.3.1?!? Anyone can
reproduce that and eventually also come up with a workaround?
best regards,
jens
--
Dr. Jens Langner
Institute of Radiopharmacy
Department of Positron Emission Tomography
Helmholtz-Zentrum Dresden-Rossendorf
Bautzner Landstraße 400!
| 01328
Dresden
http://www.hzdr.de | +49 351 260 2757
------------------------------------------------------------------------
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
