When I add an opendocument login token, it wipes out my parameter/prompt response in the Redirect URL

Question

I am having this issue and I wonder if anyone has any pointers?
When I send the URL with the single prompt response &lsSPrompt0=1234567 it works fine but I have to login to InfoView.
So I created a login token .jsp and that took care of the login for InfoView, but it also killed my prompt value.
The code that I got from another site that does the same thing I WANT to do seems to create a cookie to store the passed prompt value in, then it creates a login token, then it assembles it all in the redirect URL and sends it to the openDocument.jsp.
The login token works like a champ, but the prompt value (initially passed in to the cookie as "Prompt0") ends up passing from the Redirect URL to the openDocument.jsp with a value of NULL (lsSPrompt0=NULL).
In my lack of knowledge, I am thinking maybe it has something to do either with how the cookie is being created, how it is being passed, or how/if it is getting stored at the target.  The cookie/token.jsp and the openDocument.jsp are in different folders on the same domain.
So, I pass this URL:
http://server:8080/InfoViewApp/token.jsp?&lsSPrompt0=1234567
The token.jsp that it hits looks like this:
So, the redirect winds up hitting the target looking like this:
http://server:8080/OpenDocument/opendoc/openDocument.jsp?token=logonToken&iDocID=45227708&sKind=FullClient&lsSPrompt0=NULL&NAII=N&buttonrefresh=hide&buttonexport=hide
Obviously, my problem is this:  lsSPrompt0=NULL
Any pointers or nuggets of wisdom are GREATLY appreciated?
Also of note, I wasn't sure if I needed to publish this token.jsp as a Webapp to Tomcat.
I just placed the .jsp file in the folderTomcat5.5/webapps/InfoViewApp (same location as the client who has it working).
Do I need to publish it?  Is that part of the problem?
I am a little out of my realm here but trying to learn!
We are on BOXI R2, Tomcat 5.5, JAVA, and I am having the same behavior on my personal XI 3.0 server too
Thanks in advance,
Randy

Answer 1

I believe it's storing the info in a cookie so that it can be used later.  You don't mention which version of BO you're using, but I've sometimes found that the logon tokens created in 4.x contain special characters and may need to be URL encoded.  Also, I've found that it helps to put the logon token at the end of the URL after any parameters instead of in the middle before the parameters.
-Dell