I'm having trouble getting WAP users logged in so their user ID's can
be verified. The problem occurs on code backported from the WAP
module in ACS Classic 3.9(?) to OACS 3.2.5.
Using log notices to debug, I see that the initial call to log in the
user is completing successfully, as their user ID can be verified
from the login page using ad_verify_and_get_user_id,
immediately after it executes ad_user_login -forever t $db
$user_id. However, as soon as they are redirected to one of
the other pages they can no longer be verified as being logged in.
Using the OpenWave simulator, I can see that the usual cookies are
getting written to the device, although I have little knowledge of
how this works on wireless devices.
The pages are restricted using
wap_maybe_redirect_for_registration, which makes a call
to ad_verify_and_get_user_id to see if the user is
logged in. On any page after the login page, the user ID is returned
as "0", sending them in a circle. This can get pretty boring after
10 or 12 tries, especially with those convenient cell phone keypads.
Has anyone else wrestled with this? TIA for any help, suggestions,
or commiseration.
