F5 V11.2.1 upgrade from 10.2.4 - Can't get portal authentication to work

I attempted to do an upgrade on our F5s this past weekend. I hit a few snags here and there, but mostly have the configuration corrected and moved over.

The primary system the load balancer is working with has 3 web application servers that need session persistence from clients and are being load balanced (round robin). I've got source-address affinity and match across virtual servers to handle redirects from port 80 to 443 and back through the login process. (You'd have to ask the app guys why we don't just stick to 443)

After the problems I had Sunday, I decided to break our active/passive device trust and go to 2 standalone units so I could test v11 and get it working. Right now, my problem is: I attempt to login and I get messages stating that the username/password isn't correct. I have confirmed that persistence isn't an issue between the login page and when I go to the nonssl URL and do a check there. In testing, I was able to login successfully twice. My password is not that difficult, but does have a special character in it. (I type this password a lot, so I know it's not user error)

I don't have this problem with 10.2.4 and it's running live now. The configuration on 11.2.1 continually gives me username/password errors. Could the http profile be to blame? I'm not sure the best way to troubleshoot, but I'm going to look at using tcpdump...just wondered if anyone has any ideas of something aside from doing a full packet analysis to figure it out.

Thanks.