I have found so much in the archives that was 'cut and paste' as you
say...when I get the help to the problem from the list I try to contribute
back to it..:)

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Thad K Esser
Sent: Monday, May 14, 2007 11:07 AM
To: arslist@ARSLIST.ORG
Subject: Re: Login.jsp Manipulation


** 
LJ, 

Thank YOU for posting your final solution.  This is one of those, "gee it be
nice to fix if I had time" things, but not really on anybody's priority list
here.  I read the responses to your original post with interest, but as I'm
not a web guy, I didn't have time to try to actually understand them or turn
them into something workable. 

I appreciate the time you took to share a final solution that is basically
cut-n-paste-able.  Gotta love the list. 

Thanks again,
Thad Esser
Remedy Developer
"Argue for your limitations, and sure enough, they're yours."-- Richard Bach




"L. J. Head" <[EMAIL PROTECTED]> 
Sent by: "Action Request System discussion list(ARSList)"
<arslist@ARSLIST.ORG> 


05/14/2007 07:07 AM 


Please respond to
arslist@ARSLIST.ORG



To
arslist@ARSLIST.ORG 

cc

Subject
Re: Login.jsp Manipulation

        




As with most things I went through several iterations before I found the
eventual solution.  I will document it here for posterity sake.

When you access the Mid-Tier sever with a redirect in the URL or are
redirected by a servlet it goes into one of two variables.  Request.nextPage
(if you use the goto parameter) or session.returnBack (if you went to
/arsys/home for example).  In the login.jsp there is a hidden input field
named goto that by default value of <%=nextPage%>.  Through the assistance
of Carey and Axton I was able to modify my login_common.jsp file.  The
default line was

String nextPage = (String)request.getParameter("goto");
if (nextPage == null) {
                nextPage = "";
}

All that this section of code does is ensure that the nextPage variable is
not null.  I have modified my lines to be as such

String nextPage = (String)request.getParameter("goto");
if (nextPage == null) {
                String returnBack =
(String)session.getAttribute("returnBack");
                if (returnBack == null) {
                                 nextPage = "/arsys/home";
                } else {
                                 nextPage = "";
                }
}

What this does is if nextPage is null it then checks to see if the hidden
session variable 'returnBack' is also null.  If both variables are null you
will get an error on the home page stating that it doesn't know where to go.
So if both are null I set the nextPage variable to /arsys/home, if
returnBack is not null...I just continue the default behavior of setting
nextPage = "".  This effectively allows people to bookmark the login.jsp
page without getting errors.  It also allows for direct link URL's to allow
the user to get directly to their record.

I would like to thank the community once again for helping me solve yet
another issue.

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Axton
Sent: Sunday, May 13, 2007 5:12 PM
To: arslist@ARSLIST.ORG
Subject: Re: Login.jsp Manipulation

The value LJ was looking for was stored in a session attribute.  I imagine
they left the login page jsp during the 601->63 rewrite so that customers
could alter it.  If the page were served from a servlet, we wouldn't have
any place to customize the layout/fields unless we had the source to said
servlet, or some other funny hooks were there to take the place of
login.jsp.

Axton Grams

On 5/13/07, John Baker <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I was explaining this problem to a UK Remedy customer only on Friday. 
> Frankly, the entire "redirect to /shared/login/login.jsp" logic is 
> utterly bizarre and I can only assume that a newbie was given the task 
> of writing this bit of the Midtier. Clearly, if one goes to 
> /arsys/home and is not logged in, a login page should be presented without
a browser redirect.
>
> However, onto the matter in hand, can we establish if the goto 
> parameter is set when a user goes directly to a form entry? I.e. go to 
> a form entry when you're not logged in, and when presented with the 
> login page, paste the contents of the form. Once you've done that we 
> can address the problem in more detail (as we don't appear to have
established this yet).
>
>
>
> John
>
> Java System Solutions : http://www.javasystemsolutions.com
>
> ______________________________________________________________________
> _________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org 
> ARSlist:"Where the Answers Are"
>

____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"

____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"




***IMPORTANT NOTICE: This communication, including any attachment, contains
information that may be confidential or privileged, and is intended solely
for the entity or individual to whom it is addressed. If you are not the
intended recipient, you should delete this message and are hereby notified
that any disclosure, copying, or distribution of this message is strictly
prohibited. Nothing in this email, including any attachment, is intended to
be a legally binding signature.***


__20060125_______________________This posting was submitted with HTML in
it___

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to