Le Mer 20 Fév 2013 13:46:38, dfrett a écrit :
Show quoted text> Hi,
> I just packaged up some work I did on adding LT support a few months
> ago and pushed it to
> github [1]. I believe the code is complete, but I haven't tested it
> yet, so it might need some
> fixes.
Hi Daniel.
I tested it, it's better, but it's not sufficient.
Here are the traces in CAS server log for release code:
"POST /cas/login HTTP/1.1" 200 5610 "-" "libwww-perl/6.04"
"GET /cas/login?service=http%3a%2f%2flocalhost%2f HTTP/1.1" 200 6222 "-"
"libwww-perl/6.04 CAS-UserAgent/0.9"
Here are the same for the updated code:
"GET /cas/login?service=http%3A%2F%2Flocalhost%2F HTTP/1.1" 200 6222 "-"
"libwww-perl/6.04"
"POST /cas/login HTTP/1.1" 302 - "-" "libwww-perl/6.04"
"GET /cas/login?service=http%3a%2f%2flocalhost%2f HTTP/1.1" 200 6222 "-"
"libwww-perl/6.04 CAS-UserAgent/0.910"
The 302 response status to the POST request show than authentication
succeed, but the agent is unable to extract the ticket from the location
header in the response.
Here are the traces with an actual browser:
"GET /cas/login?service=http%3a%2f%2flocalhost%2f HTTP/1.1" 200 6083 "-"
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1"
"POST /cas/login?service=http%3a%2f%2flocalhost%2f HTTP/1.1" 302 -
"
https://cas.domain.com/cas/login?service=http%3a%2f%2flocalhost%2f"
"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.1"
"GET
/cas/serviceValidate?service=http%3a%2f%2flocalhost%2f&ticket=ST-19-NLTY4m60vKnWELBfMoGZ-localhost
HTTP/1.1" 200 174 "-" "mod_auth_cas 1.0.9.1"
The main difference seems to be than the service is passed as a
parameter URL when posting. I'll try to adapt the code myself.