On Fri, Aug 16, 2013 at 4:06 PM, Chris Geer <[email protected]> wrote:
> We converted our system over to use Embedded Experience only to find we > have a major problem and I don't have a good solution as of yet. Hoping > someone can help. > > We host a Rave server behind a reverse proxy, and that proxy handle all the > URL mapping from our internal names to the external names. All of this > works wonderfully, except for Embedded Experience. The challenge we have > with embedded experience is that we have to refer to the widget we are > trying to load by it's URL, instead of an ID. Since the widgets are > registered with an internal URL, when they show up on the external side > nothing works because it tries to load from a bogus url. If I use the > reverse proxy to "fix" the URLs, then embedded experience fails because the > the "fixed" url doesn't match whats in the DB. > > I tried Shindig rewrite, but that doesn't work either because our server > actually backs multiple URLs so it's not fixed. > > Would there be any way to reference a widget by name instead of by URL? > > Currently, the OpenSocial client injects a controller that acts like a service to generate the security token for the EE, It verifies the URL exists in the database. with the API rewrite, I think we should allow providers and downstream implementers to easily inject their own additional APIs. When we do this, we could expand the OpenSocial API to have a generate token from widgetId instead of URL. Until then, you could do the same in the SecurityTokenController in the OpenSocial provider. > Chris >
