11-10-2010 01:29 PM
The problem is that I would like to continue using the errorbox object (it's the same form, why not) but the behaviors are different. When a user fails login at the default CP login page (invalid email address, user/pass auth fail), the form reloads the CP login page with the errorbox filled in. Unfortunately, users who fail login using the custom CP page receive a HTTP 302 redirect to my CP login with an "errmsg" value set. Not the same, so the errorbox never gets updated and they will potentially keep bashing their heads (and smartphones) against the login page.
Anyone seen this before? And have a solution other than a completely external CP setup??
11-10-2010 06:04 PM
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
Validated Reference Design Guides : http://community.arubanetworks.com/t5/Validated-Reference-Design/tkb-p/Aruba-VRDs
11-11-2010 09:31 AM
11-11-2010 09:58 AM
POSTing this to /cgi-bin/login - "email=abcdef&cmd=authenticate&Login=Log+In" and I get the 302 redirect to this location - "/upload/custom/utest-captiveportal-profile/CPLogi
This would be fine and I assumed that "errmsg" was a variable in the stylesheet, but there doesn't seem to be any reference to "errmsg" in the HTML or the CSS. Nor is there any reference to "errmsg" in the ExternalAuth-v2.30.doc file, so I'm wondering if I simply tripped over an undocumented oddity in the CP login script on the controller ??