Hi Anand,
The security token bits of php shindig are known to be working.. you
can see a live version of it in action on www.partuza.nl if you
subscribe to the 'seeing is believing' point of view :P
My hunch is that your error is created by either:
- the time skew between your SNS / iframe generating server, and
shindig server. There is an expiration max time encoded into the
token, so if the clocks between the two are very out of sync, you
would get such an error.
or
- Your running a new PHP Shindig with an old Partuza, or visa versa.
In the course of the 0.8 / REST API work the token encoding was
changed since it's being parsed along differently then it was in the
0.7 days, so if you are not running the most up to date version of
either, that could also explain the error.
Hope that helps!
-- Chris
On Aug 22, 2008, at 9:49 AM, anand sharma wrote:
Hi to All
i was just looking on PHP Shindig security token , whenever
in shindig->php->config->container.php , "allow_plain_text"=
"TRUE" , it
will call Basic SecurityToken.php ( Extends SecurityToken.php) and
BasicSecurityTokenDecoder.php (Extends SecurityTokenDeccoder.php)
and set the value of Token .
I hope whatever i understand is okie .
But when "allow_plain_text"="False", its giving output like :
500 Internal Server Error
Message: INVALID_GADGET_TOKEN
GadgetException Object
(
[message:protected] => INVALID_GADGET_TOKEN
[string:private] =>
[code:protected] => 0
...................................................................
But i think it doesnot suppose to give Error like this .
is it neccessary to set value as "TRUE" to "allow_plain_text" in
php->config->container.php
Cheers
Anand
