01-20-2016 05:49 AM
I am troubleshooting setting up an external captive portal on an IAP running 126.96.36.199-188.8.131.52_52602.
The issue appears to be when using "authentication text" as the type in for the profile and putting a url, ie "/xyz/abc.html" --> it does not redirect at all. When I tested with a different site which did not have a URL it redirected correctly.
Interstingly when the authentication type was "radius authentication" and I had a url for redirection it redirected correctly....
Am I missing something obvious? Thoughts?
Thanks in advance.
01-20-2016 12:14 PM
ACDX #420 | ACMP
[If you found my post helpful, please give kudos!]
01-21-2016 11:18 AM
It actually appears that the extra stuff the IAP appends to the url, my captive portal/webserver can't deal with resulting with error 500.
The example of where it worked seems that that webserver was able to process it. I am checking to see if there is a specific config on it.
01-23-2016 06:26 AM - edited 01-23-2016 06:36 AM
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
02-05-2016 12:41 AM - edited 02-05-2016 01:13 AM
Any updates to this problem?
I'm facing a somewhat similar problem, a hotel shall utilize an external captive portal residing on the Internet, and thus we use https.
Guest portals using https can be a bit tricky i'm told, and the experience is that users running windows 10 have problems displaying the portal page. Not sure if this is related to OCSP or what, as i'm unable to re-create the problem in my lab with similar equipment.
Instant is running version 184.108.40.206-220.127.116.11
02-08-2016 12:27 AM
I did wonder about that when posting.
Found some solution to the problem though.
As i didn't program a specific role for the captive portal, and used the role the system gives med (external CP), i could see that the system was inconsistent in giving the right role to clients.
Not all users where given this role, so they did not get the portal because of the wrong role.
Instead i created a CP logon role, assigned this role to the pre-authentication role on the role-based access rules.
This gave me more accurate assignment of roles than before.