GenerateURL within LoginAuthUser and passing parameters to a portlet in 6.1   

Using Portal 6.1.01. I'm using the url generation discussed in http://www-01.ibm.com/support/docview.wss?rs=688&uid=swg21265900. The generation code is directly from wp.l2.urlhelper.jar attached to that document.

I'm in the LoginUserAuth class in doPostLogin, so my user has authenticated. I am using the below code to generate a url to a specific page (authenticated) within portal and portlet. I'm trying to pass parameters from LoginUserAuth to the portlet so I can use them in the render phase. Here is the snippet of code:
ObjectID pageoid = IdentificationHelper.getObjectID(REDIRECT_PAGE_OID);
ObjectID portletoid = IdentificationHelper.getObjectID(REDIRECT_PORTLET_OID);
targetURLStr = OffLineURLHelper.generateUrl(pageoid, portletoid, map, serverContext, true);
runData.setRedirectURL(targetURLStr);
return;

The OIDs come directly from the xmlaccess script, so I know they are both correct. The map contains just one value that needs to be passed to the portlet.

When this runs, my user is redirected to the correct page in Portal and the portlet displays on the page. However, no parameters appear in the render phase according to the code below.

In the portlet code, I do the following:
public void doView(RenderRequest request, RenderResponse response) throws PortletException, IOException {
log.debug("Process the view");
Enumeration enummer = request.getParameterNames();
while(enummer.hasMoreElements()){
String parmName = (String) enummer.nextElement();
log.debug("Render param = " + parmName);
}
....
My log shows that I got to the render phase OK, but there are no parameter names showing up.

Any suggestions for what could be wrong? Is it possible to pass render parameters from the offline url generation while in LoginUserAuth?

Sorry, but, in a standard portlet, you can't access the parameters of a url in that fashion.

The code snippet given is for a standard portlet itself. I am getting the values from the url.
Pls refer it once.

Yes the query string is not coming in Portal v 6.1 whereas its coming in 6.0.

Sorry, I did not find a solution to this.

Two things to remark

Because the first generated URL is targeting to a unprotected area, but the authentication had been finished already Security does force a logout. This logout does stop the parameters for the JSR168 Portlet been added to the State of the current executed request.

The 2. problem which occurs (if you send it to a protected URL, may be caused by the Code made available in the technote. The error does show that an action is send to a portlet (what you expect) but Portal does expect in such case an action ID to track the action and prevent double execution.

You cannot get query string parameters in JSR 168 portlets - the jsr spec doesn't allow portlets to get the query string.

Here are a couple of thoughts.
1. If you are trying to send data from one portlet to another, the way to do that is via wiring, not the query string. It sounds like you have that working somewhat. You will need to set up WSDL files in both portlets - the source will publish your id and location values, while the target portlet will consume them.

2. If you move up to JSR286 portlets, you can set public render parameters in the source portlet and then grab those render parameters in the target portlet.

3. If you are trying to pass parameters from outside of portal (like in a servlet, for example) and you want to target the parameters to a specific portlet, you can use Portal's URI Resolver service. The following article explains it pretty well, but you will have to modify it to target just one portlet. http://www.ibm.com/developerworks/websphere/library/techarticles/0710_koeth/0710_koeth.html

Passing parameter to a portlet: Were you able to resolve this? I Have a similar requirement like this. Any help is highly Appreciated.
Thanks
Gigi