I had this problem with the Sentinel ASP client in IIS, and traced it
back to the Global.asa file not being in the root of the website. So the
Sentinel Application was not being initialized, and so it wasn't working
correctly. Not sure if this helps at all, but figured I'd pass it on
anyway.
Chris Harper
INFORMATION TECHNOLOGY SPECIALIST
University Relations / Michigan State University
1330 S. Harrison Rd., East Lansing, MI 48823-5200
Email: [log in to unmask] / Office: 517.355.6611 x 103
Web: http://ur.msu.edu / Cell: 616.291.1987
-----Original Message-----
From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of Eric Weston
Sent: Friday, April 14, 2006 11:30 AM
To: [log in to unmask]
Subject: [MSUNAG] Sentinel under non-MS systems
Anyone have experience using Sentinel on systems other than MS IIS
serving .asp pages? I'm trying to get Sentinel working, using the php
sentinel client, on a Red Hat Enterprise AS v.4 server running Apache
2.0.52 and PHP 4.3.9. Both apache and php are the packages shipped with
Red Hat AS4.
The php.ini file has a note that it contains default settings that
may differ from standard settings (sadly typical of Red Hat). Here is
the note:
" This is the recommended, PHP 4-style version of the php.ini-dist file.
It sets some non standard settings, that make PHP more efficient, more
secure, and encourage cleaner coding.
The price is that with these settings, PHP may be incompatible with
some applications, and sometimes, more difficult to develop with. "
I suspect one of the "non standard" settings is making our php instance
incompatable with AIS's sentinel php client. I'm not very experienced
with PHP, so I've had no luck isolating the offending setting, if that
is indeed the problem.
I should point out that the authentication itself does work; the
failure is that the session variables that contain credential/identity
info are failing to store in the session. There should be publicID,
firstName, and lastName data stored in the session, but this is not
happening. Cookies are working, and Sentinel returns the "Token" url
variable after authentication, but no session variable(s).
Any ideas?
Eric Weston, Library
|
