SSO for webserver

ok - thanks - cut'd the code and created a new iRule which is fired as the first on my test-vs - I'll try to trace what happens when this iRule is fired.

 

 

best regards /ti

Hi Again

 

Looks as if the script Works - added a bit debug around it and it is triggered etc - looks fine - thanks

 

But - I am still fighting with the problem about get a persistent APM session up - I debugged with tcpdump on the F5 and it looks to me that the Cookie is modified in the F5? I have defined a wrong cookie in the SSO Form so when I changed it to the value I could trace in tcpdump my SSO seems to work (more investigation needed)

 

But - after this I am back with my other problem - corrupted Java script when succeding in getting the APM session persistent - which again must be somthing with the chunking.

 

Even though the iRule modfies the request I can change the behavior of the flow with the chunking settings in the HTTP profile

 

When I define "Request Chunking"="Preserve" or "Selective" and "Response Chunking"="Selective" the APM module succed in detecting the logon but then I then come to the next form on the webpage this will be corrupted when loaded.

 

If set to "Preserve" in both directions the APM module fails in detecting the logon

 

so - hmm - can I control the Chunking with that iRule ? As far as I have understod the chunking is just a sort of sending a webpage as one page but in fragments - is that correcft understood?

 

 

best regards /ti

 

 

Yes, chunking is a way of breaking messages up into smaller pieces. It's generally used to facilitate streaming data where you may not know in advance what the total payload size will be or if you want page content to start rendering before all of the data is sent (or generated). The above iRule tells the server that the client cannot handle chunking, by essentially disabling HTTP 1.1. It also tells the server not to compress the response. If you suspect that chunking is still happening, observe the response data in the capture. By the way, you may have a better time by at least analyzing the TCPDUMP data in Wireshark, if not capturing it there. Chunking will be evident by the "Transfer-Encoding: chunked" header. You may also notice whether or not the payload looks compressed (unreadable).

 

 

As for the Form SSO settings, you need to find at least one event that is unique to a successful logon. You're best bet again is to capture that process (I recommend Fiddler of IEWatch in the browser, but also Wireshark) to see what happens directly before and directly after a successful logon. You can attach that capture here if you'd like us to take a look.