You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@shindig.apache.org by Pablo Graña <pa...@globant.com> on 2010/07/13 19:32:54 UTC
secured and DefaultServiceFetcher
Hi:
When I configure shindig in secured mode, the first time I display a gadget
that accesses the activity api, shindig shows this in the console:
Jul 13, 2010 1:48:25 PM
org.apache.shindig.gadgets.render.DefaultServiceFetcher retrieveServices
SEVERE: Failed to parse services methods from endpoint
http://localhost:8098/katari-sample/module/shindig/gadgets/api/rpc.
JSONObject["data"] not found.
This looks like it is due to an internal http request
that DefaultServiceFetcher does without a security token. What I did as a
work around was to create a security token for a fake user.
Single stepping a little bit in the code, this problem should also happen
independently of the security mode, but I could be wrong.
thanks a lot
--
Pablo Gra\~na
Chief Architect
Globant
Arg Office: +54 (11) 4109 1743
UK Office: +44 (20) 7043 8269 int 8043
US Office: +1 (212) 400 7686 int 8043
Re: secured and DefaultServiceFetcher
Posted by Paul Lindner <pl...@linkedin.com>.
That's correct.
2010/7/20 Pablo Graña <pa...@globant.com>
> So, the DefaultServiceFetcher is sort of an optional component, we can get
> away without it if we specify all the endpoints in container.js, right?
>
> thank you
>
> On Tue, Jul 20, 2010 at 10:58 AM, Paul Lindner <plindner@linkedin.com
> >wrote:
>
> > Yes, this is expected. If you cannot run the system.listMethods then
> > shindig cannot
> > populate the endpoints, you need to specify them in container.js
> manually.
> >
> > It may be possible to populate this information without hitting that
> > endpoint -- things get complicated if you have separate servers for
> > gadgets/social
> >
> > 2010/7/13 Pablo Graña <pa...@globant.com>
> >
> > > Hi:
> > >
> > > When I configure shindig in secured mode, the first time I display a
> > gadget
> > > that accesses the activity api, shindig shows this in the console:
> > >
> > > Jul 13, 2010 1:48:25 PM
> > > org.apache.shindig.gadgets.render.DefaultServiceFetcher
> retrieveServices
> > > SEVERE: Failed to parse services methods from endpoint
> > > http://localhost:8098/katari-sample/module/shindig/gadgets/api/rpc.
> > > JSONObject["data"] not found.
> > >
> > > This looks like it is due to an internal http request
> > > that DefaultServiceFetcher does without a security token. What I did as
> a
> > > work around was to create a security token for a fake user.
> > >
> > > Single stepping a little bit in the code, this problem should also
> happen
> > > independently of the security mode, but I could be wrong.
> > >
> > > thanks a lot
> > >
> > > --
> > > Pablo Gra\~na
> > > Chief Architect
> > > Globant
> > > Arg Office: +54 (11) 4109 1743
> > > UK Office: +44 (20) 7043 8269 int 8043
> > > US Office: +1 (212) 400 7686 int 8043
> > >
> >
> >
> >
> > --
> > Paul Lindner -- plindner@linkedin.com -- linkedin.com/in/plindner
> >
>
>
>
> --
> Pablo Gra\~na
> Chief Architect
> Globant
> Arg Office: +54 (11) 4109 1743
> UK Office: +44 (20) 7043 8269 int 8043
> US Office: +1 (212) 400 7686 int 8043
>
--
Paul Lindner -- plindner@linkedin.com -- linkedin.com/in/plindner
Re: secured and DefaultServiceFetcher
Posted by Pablo Graña <pa...@globant.com>.
So, the DefaultServiceFetcher is sort of an optional component, we can get
away without it if we specify all the endpoints in container.js, right?
thank you
On Tue, Jul 20, 2010 at 10:58 AM, Paul Lindner <pl...@linkedin.com>wrote:
> Yes, this is expected. If you cannot run the system.listMethods then
> shindig cannot
> populate the endpoints, you need to specify them in container.js manually.
>
> It may be possible to populate this information without hitting that
> endpoint -- things get complicated if you have separate servers for
> gadgets/social
>
> 2010/7/13 Pablo Graña <pa...@globant.com>
>
> > Hi:
> >
> > When I configure shindig in secured mode, the first time I display a
> gadget
> > that accesses the activity api, shindig shows this in the console:
> >
> > Jul 13, 2010 1:48:25 PM
> > org.apache.shindig.gadgets.render.DefaultServiceFetcher retrieveServices
> > SEVERE: Failed to parse services methods from endpoint
> > http://localhost:8098/katari-sample/module/shindig/gadgets/api/rpc.
> > JSONObject["data"] not found.
> >
> > This looks like it is due to an internal http request
> > that DefaultServiceFetcher does without a security token. What I did as a
> > work around was to create a security token for a fake user.
> >
> > Single stepping a little bit in the code, this problem should also happen
> > independently of the security mode, but I could be wrong.
> >
> > thanks a lot
> >
> > --
> > Pablo Gra\~na
> > Chief Architect
> > Globant
> > Arg Office: +54 (11) 4109 1743
> > UK Office: +44 (20) 7043 8269 int 8043
> > US Office: +1 (212) 400 7686 int 8043
> >
>
>
>
> --
> Paul Lindner -- plindner@linkedin.com -- linkedin.com/in/plindner
>
--
Pablo Gra\~na
Chief Architect
Globant
Arg Office: +54 (11) 4109 1743
UK Office: +44 (20) 7043 8269 int 8043
US Office: +1 (212) 400 7686 int 8043
Re: secured and DefaultServiceFetcher
Posted by Paul Lindner <pl...@linkedin.com>.
Yes, this is expected. If you cannot run the system.listMethods then
shindig cannot
populate the endpoints, you need to specify them in container.js manually.
It may be possible to populate this information without hitting that
endpoint -- things get complicated if you have separate servers for
gadgets/social
2010/7/13 Pablo Graña <pa...@globant.com>
> Hi:
>
> When I configure shindig in secured mode, the first time I display a gadget
> that accesses the activity api, shindig shows this in the console:
>
> Jul 13, 2010 1:48:25 PM
> org.apache.shindig.gadgets.render.DefaultServiceFetcher retrieveServices
> SEVERE: Failed to parse services methods from endpoint
> http://localhost:8098/katari-sample/module/shindig/gadgets/api/rpc.
> JSONObject["data"] not found.
>
> This looks like it is due to an internal http request
> that DefaultServiceFetcher does without a security token. What I did as a
> work around was to create a security token for a fake user.
>
> Single stepping a little bit in the code, this problem should also happen
> independently of the security mode, but I could be wrong.
>
> thanks a lot
>
> --
> Pablo Gra\~na
> Chief Architect
> Globant
> Arg Office: +54 (11) 4109 1743
> UK Office: +44 (20) 7043 8269 int 8043
> US Office: +1 (212) 400 7686 int 8043
>
--
Paul Lindner -- plindner@linkedin.com -- linkedin.com/in/plindner