shindig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sumedha Sanjeewa <>
Subject Re: OAuth Error with Shindig
Date Tue, 05 Jul 2011 06:08:13 GMT

I was able to fix the problem. What I did was changing the method
createToken() in the CommonContainerSecurityTokenCodec class. In the trunk
it is implemented as

  public SecurityToken createToken(Map<String, String>
tokenParameters)throws SecurityTokenException {

    TestSecurityTokenCodec testSecurityToken = new TestSecurityTokenCodec();
    return testSecurityToken;


I changed the method to use BasicSecurityTokenCodec instead of

  public SecurityToken createToken(Map<String, String> tokenParameters)throws
SecurityTokenException {

    BasicSecurityTokenCodec basicSecurityTokenCodec = new
    return basicSecurityTokenCodec.createToken(tokenParameters);


When I was debugging the code I noticed that the security token was not
passed in the fetch method in OAuthRequest class. When I traced this and
compared with Shindig 2.0.0, I found that current revision uses the
instead of BasicSecurityTokenCodec.

So after the above modification It worked fine and all the other
modifications I had mentioned in the above reply's are not needed. This is
the only place that has to be modified.

So is this modification correct..??

Thanks for your help guys....

On Mon, Jul 4, 2011 at 8:21 PM, Evgeny Bogdanov <>wrote:

> I suggest you create your own keys (at least that's what i did). The ones
> in the example
> might not work anymore (expired or something ...)
> On 04.07.11 15:18, Sumedha Sanjeewa wrote:
>> No. They are from the example. BTW I noticed that in the above error my *
>> oauth_signature_method="RSA-**SHA1"*.
>> But In the oauth.json the key type is set as *RSA-PRIVATE*.
>> Is this related to the error I'm getting.

Sumedha Kodithuwakku

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message