Some versions ago, I tried to create a remote content link to an application that needed to know the user name of the current user. At that time, there was no way to pass the current user to the nested app. I have noticed I can now add keyword replacements into the post variables section of the remote content asset, but I have searched high and low for a keyword replacement for the user name of the current user.
We are using 3.10 (about to upgrade to 3.12) - is there any keyword replacement that I can use? The user name in any form would be enough - I can write the app at the other end accordingly. Last time I worked out a complicated way through cookies, but it was not very successful, so noone really used it!
You can use %globals_user_attribute_username% in the POST vars to post the current username.
Hi I have a similar problem, users submit their username served remotely and I want to send the post value back to the same page so the db and can do its thing and display a message, I have tried various options with tunneling and Post Data options with no luck 
any advice is appreciated
Matrix can only post values it knows, so the only keywords available are for Matrix attributes (like Matrix username). Where are you getting the username from?
the username is entered from a page being remotely served from our old zope site, I then want to send the value back to the page
Are you sure it is not being sent back already?
Zope won't properly set AUTHENTICATED_USER from post variables without something like the cookie crumbler product being used, and I am not sure how well remote content plays with cookies for remote sites.
If you put <dtml-var REQUEST> into remote zope page you are trying to get to then you will be able to confirm if the entered values are being put into the request.
The experience I have had so far with 3.14.2 Matrix and zope shows that Matrix does send through every post or get variable as part of the request.
(nb. sorry if this is pitched below you, not sure what your zope experience is)
Matrix has a session/cookie handler built-into the Remote Content so it should maintain sessions that start within the remote content asset itself. If you login outside remote content, Matrix can't maintain that session.