05-10-2017 08:02 AM
05-16-2017 02:32 AM
Thanks, this looks pretty cool!
Though, I should recommend against putting content like this on the controller. The controller is not designed to be a web server, hosting content like this and in environments where you have more than just a few users, this can result in serious issues.
If you can place the content on an external web server, and white-list access to that server from the guest's login role, you can still host the content and use an external captive portal for that.
The authentication POST from the index.html:
... method="POST" action="/auth/index.html/u" ...
.. should be changed to have the full https://<name-of-the-controller-certificate> in the action.
Another benefit is that if you have multiple controllers, there is no need to put the content on each of them. Also, the content management may be easier as it may be managed with the tools you have in place already for internet or intranet websites.
If you have urgent issues, please contact your Aruba partner or Aruba TAC (click for contact details).
05-16-2017 02:49 AM
I completely agreed, since the controller memory is limited, it is better to offload this page to other web server.
For information, I have tested it on my 3400 and it looks like the controller can handle it well. But, when i try to upgrade it, there is not enough memory left to do the task.. :)