Hi Auninda,
that is a good possibility. The phpcas client uses the php curl library
to connect to the cas server to validate the ticket.
You might have to use the phpCAS::setExtraCurlOpts() [1] function to
configure the the proxy settings. phpcas uses the curl_setopt_array()[2]
function.
Without having tested it you might need add something like the following
behind the phpcas initialisation (add your settings of course):
phpCAS::setExtraCurlOpts(array(CURLOPT_PROXY =>
'http://myproxy.com:1080',
CURLOPT_PROXYUSERPWD => 'user:pwd"));
Regards,
Joachim
[1]
http://downloads.jasig.org/cas-clients/php/current/docs/api/classphpCAS.html#a26ba0156e03fede5cd0c6bacbae8e928
[2] http://www.php.net/manual/de/function.curl-setopt-array.php
Am 02.12.2011 11:39, schrieb Auninda Rumy Saleque:
hey thankx for the reply. ill have to look into it sometimes tomorrow as
i am away from all of my setup for the next 24hours. i do have doubts
that my working behind a proxy may be the reason for all of this. but
lets see.
Regards,
Auninda
On Fri, Dec 2, 2011 at 2:44 PM, Joachim Fritschi <[email protected]
<mailto:[email protected]>> wrote:
Hi,
please enable the phpCAS debug log [1]. Maybe that can be done in
the config menu or you can just search the cas plugin code for any
phpCAS::client() or phpCAS::proxy() call and add an
phpCAS::setDebug($filename) directly after those calls.
The debug log should give you a pretty good idea about anything that
is happening with the cas client.
Regards,
Joachim
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-dev
