The warnings come from invalid HTTPS certificates, as you seem to have found out already.
Depending on where in the authentication process the warning comes up, that can be during the original redirect to the captive portal, or for the actual authentication (credentials post to securelogin.arubanetworks.com), there are different solutions.
For the first issue, the initial re-direct, please read this blog post: http://community.arubanetworks.com/t5/Technology-Blog/Captive-Portal-why-do-I-get-those-certificate-warnings/ba-p/268921 and follow the suggestions to get rid of that warning.
If the warning is when you try to post your credentials, the 'use HTTP' should work as it does not use HTTPS. Please note that if you switch to HTTP the username and password are sent 'in clear' and can be captured if they are on an open SSID.
My advice would be to fix your certificates. Check this FAQ: http://community.arubanetworks.com/t5/Controller-Based-WLANs/ArubaOS-Default-Certificate-Revocation-FAQ-Controllers/ta-p/275809 on how to get the proper certificate installed. Just if you understand the consequences (username/password sent in the clear), you should move to HTTP authentication.