I would compare the HTML with a unmodified login page. The action should probably include the reference to your controller, not just /auth which is local on the web server (which is ClearPass). You may have found that URL in references for the internal captive portal for the controller, in which case you can use a relative url.
Try to change to something like: 'action="https://captiveportal.yourcompany.com/auth/index.html"' change the hostname to what is the hostname/fqdn for the certificate installed on your controller for captive portal.
Personally I find it always useful to use the network trace in the developer tools of your browser and follow the steps in the guest workflow. That probably would have exposed this, that the request was going to ClearPass instead of to the controller.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Dec 02, 2024 10:06 PM
From: Ronin101
Subject: Custom login form
Dear Experts,
I am using custom login form in the login page of the self registration. I saw that the action should be action="/auth/index.html/u". However in my case its not posting to the controller but reverts back to CPPM main page. I am not sure how it works or what am i missing? is this the right action to be taken when submit button is clicked?