Wallace,
One thing you could do is actually log in for the user. In other words, the
link would go back to your servlet, and your servlet would act as a proxy
and open its own URLConnection that posted the data to the other site's
login page. It would then simply forward the response back to the user...
There may be some performance considerations to this approach...
Just my two cents....
<<KM>>
[EMAIL PROTECTED]
Friday April 14, 2000 04:56 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc: (bcc: Kito Mann/PSG/Prudential)
Subject: Re: re-authenticate
Greetings,
We have developed a secure site using ssl & java servlets.
We have a secure servlet that does custom authenticate ( ssn, pin )
using jdbc.
We have a link on our menu that navigates to another secure site.
It uses another custom authenticate scheme to validate users.
My question is ...
How can we avoid having the user re-authenticate to the other site?
Do we simply encode the user's ssn & pin into the link?
Is there another way?
Thanks.
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
