Title: Please help. Accessing protected url from java when using form based authentication
You must unsubscribe yourself. 
 
Here's some info posted by another user about unsubscribing:
 
 
it is a little tricky to unsubscribe from tomcat-user
when you have changed your e-mail address and need to
use this
 
 [EMAIL PROTECTED]
 
to unsubscribe. Some mail clients like MS-Outlook have
trouble with the equal-sign "=" in the recipients address.
Here's the e-mail header you sent. If you look closely at
the "To:" line, you will see what has happened:
 
> To: 'tomcat-user-unsubscribe-lmayer=' <[EMAIL PROTECTED]>
 
Your e-mail client has split the recipients address at the "="
into the display name ("tomcat-user-unsubscribe-lmayer=") and
the e-mail address ("[EMAIL PROTECTED]").
 
Somehow you need to make sure that your e-mail client
really sends a message to
 
 [EMAIL PROTECTED]
 
For MS-Outlook, the following has worked for me:
1. type the correct unsubscribe address into the "To:" field.
2. click outside of the "To:" field and watch Outlook "convert"
the address you typed into display name and e-mail address.
3. double click on the display name in the "To:" field, note
the wrong e-mail address in there and adjust the e-mail address
to the correct one.
4. done.
-----Original Message-----
From: Brian George [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 23, 2001 5:54 PM
To: [EMAIL PROTECTED]
Subject: RE: Please help. Accessing protected url from java when using form based authentication

Please UNSUBSCRIBE me.
 
I did not subscribe to this listserve.
-----Original Message-----
From: Roytman, Alex [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 23, 2001 1:26 PM
To: '[EMAIL PROTECTED]'
Subject: Please help. Accessing protected url from java when using form based authentication

I need to access a protected resource on my web site from java. I use form based authentication and I was hoping that following sequence will make it but it dos not

1. Open url to protected resource. get JSESSIONID from headers
2. Post to /mycontext/login/j_security_check with cookie set to JSESSIONID=<session id from prev step> and name and password as POST parameters

3. Access protected resource again using the same session id

Any help is greatly appreciated

Alex

Reply via email to