Forum Discussion
Hi Stanislas
Thanks for the reply and the additional information, I kind of understand what the iRule is trying to do. I will try to explained the issue we are seeing and if you could verify this will fix the issues we are seeing.
- first issue we ran into, in 11.4.1 when configuring SSO with multi-domain cookies, APM would authenticate the user but not validate the session and the log-on page (APM) will just go username and password error. The work around from F5 was to configure a base cookie for just the domain (which is what we are currently using).
we are running SharePoint2013 with Apps and OWA running through the same VIP (each one using a different sub-domain).
- With out any irules the user can open up a word,excel, powerpoint, project, document in OWA (through a browser) but when they tried to open it with the thick client the APM embeds a login page in the application asking to allow JavaScript and authenticate again.
when I used the above IRule posted by Joe, we could open documents in the thick client but a popup box would display asking the user to log in each time, a bit annoying for the user and unacceptable for the customer.
When we did further investigation it looked like it has something to do with the users computers not accepting the web cookie and turning it into a persistent cookie so applications have access to it (persistence is check on the single base cookie).
can you validate what the irule does and the likely hood it would solve our problem.
John Attard
- JohnA_45647Jun 25, 2015Nimbostratuswe are using the same URL's internally and externally, just rewriting to https://