I'm switching from Basic (with SSL) to Form authentication (also with SSL of course).
This has caused a problem with one particular application, which opens a socket on a .jsp page, collects the html code and saves it disk. The html code is then later used by a fax application to send a fax.
With Form authentication I am getting a login popping up, which since I have already signed in, should be unnecessary if I provide the right stuff to Tomcat.
For Basic authorization, all the application had to do was send an "Authorization" header and in I went without a login.
But with Form authentication I am unable to prevent the new login.
I assumed that setting the JSESSIONID and JSESSIONIDSSO cookies would be sufficient, and here is my code.
OutputStream out = sock.getOutputStream();
String firstLine = "GET " + fileName + " HTTP/1.1\r\n";
String secondLine = "Host: " + hostName + "\r\n";
send(out, firstLine);
send(out, secondLine);
send(out, "Set-Cookie: JSESSIONID=" + jsessionId + ";JSESSIONIDSSO=" + jsessionidSSO + "; Path=/" + "\r\n");
send(out, "\r\n");
But unfortunately Tomcat isn't impressed and I get a login page. Can anybody tell me where I'm going wrong?
Thanks.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
