Remote Content tunneling URLs created after page loads

(Huy Le Nguyen) #1

Hi there, been testing out there Remote Content Asset recently to test its capacity for nesting in ASP.NET content, seems to work pretty well, except there is a script on the page I’m nesting in which fills in some navigation links depending on whether the user is logged in.

The links created are in the same domain as the page that’s being nested in, however the tunneling properties set doesn’t seem to be working on them (maybe because the links are created after the page has loaded?), so when a user clicks on any of them, they get directed to the page being nested (instead of staying on the Remote Content Asset page).

Any idea what my options may be to solve this?

(Bart Banda) #2

If the links are being created after page load, there’s probably some JS in place that is doing it. Perhaps you need to write your own JS that runs after the original JS, which in turn changes the links again?

(Huy Le Nguyen) #3

So I’ve done a bit more digging around where the problem might be (not a lot of debugging information to work with for Remote Content Assets), and I found that the links that are generated on the Remote Content page mirror the links generated on the actual page.

i.e. If I am logged in on the actual page, the Remote Content page will also show me the correct profile navigation, but if I am not logged in on the actual page, the Remote Content page will still show “Log in” on its navigation. However, requiring the user to log in on the actual page defeats the purpose of nesting it into the Remote Content asset.

I have no clue how to carry on :frowning:

(Bart Banda) #4

So are you trying to remote content in a page that you need to be authenticated for first to see? If that’s the case you need to look at other ways of integrating this.

Is that data allowed to be publicly accessible? The other possibility is to use a REST asset and pass username and password to the page you are requesting but it’d need to accept HTTP basic auth.