Hi Scott,
I am faced with similar issue. Will get a try .
Can you help me here with some understanding.
Step1- user types in www.google.com , WLC intervenes and redirects to the url configured under WLAN-security-external url and the override global is checked.
Step2- the login page has the username password field which user fills in and press submit.
Step3- WLC sends a http post with all the required attributes to portal which also include the username / password. In my case the construct looks like this
https://1.1.1.1/login.html?buttonClicked=4&err_flag=0&userna
me=12345&password=7476&redirect_url=https%3A%2F%2Ftestwifi.abc.in%2FCaptivePortal.do%3Fres%3Dsuccess%26userid%3D9717983832&switch_url=
https://1.1.1.1/logout.html
Step4: plc would pull out the username / password , build it in the access request and send to AAA. After receiving the access accept , which is the url that WLC should point the client to. Can you help me understand ,how does WLC treat the redirect_url string and the switch_url string from the above http post.
Step5: In my case , after step 2 , once authentication is done , the user is directed to a successful login page. I am trying to understand, from where did WLC get the url for this successful login page. , is it from step 3.
step6- on the successful logged in page of the portal there is logout button. On pressing that , i am getting the popup window which has the url pointing to
https://1.1.1.1/logout.html?redirect_url=https%3A%2F%2Ftestwifi.abc.in%2FCaptivePortal.do .
Why do i get this popup up. Is there a way i can stop this popup.
The portal is sending http post with the url https://1.1.1.1/logout.html?redirect_url=https%3A%2F%2Ftestwifi.abc.in%2FCaptivePortal.do when the logout button is pressed.
Can you point to some document which can explain the structure of the http post during the entire life cycle.
