Project

General

Profile

Actions

Bug #10430

closed

Captive Portal shows 404 post login after upgrade to 2.4.5

Added by Jimmy Chen almost 4 years ago. Updated almost 4 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
Captive Portal
Target version:
-
Start date:
04/05/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
amd64

Description

I just upgraded to 2.4.5 and when a user signs in via Captive Portal it immediately shows a "404 Not Found" nginx error. I have the After Authentication Redirect turned on, but that is not working at all. Disabling that options also yields the same 404 page.

I am using RADIUS MySQL authentication. Aside from the 404, the Captive Portal functionality is working.


Files

RPReplay_Final1586076284.mp4 (2.57 MB) RPReplay_Final1586076284.mp4 Jimmy Chen, 04/05/2020 03:47 AM
Actions #1

Updated by Jimmy Chen almost 4 years ago

Testing the Captive Portal in a Windows machine allowed me to see the URL it's hitting post login.

https://guest.example.com:8003/$portal_redirurl$

This obviously is incorrect and does not reflect the URL I configured (https://www.google.com) for the redirect.

Actions #2

Updated by Jimmy Chen almost 4 years ago

I figured out the issue. It appears to be configuration problem, possible as a result of the upgrade. The default redirect URL I had configured was https://www.google.com. Somehow, it put that was the "After authentication Redirection URL" which was the variable $portal_redirurl$. After switching these 2 values in the configuration, it's now working.

Actions #3

Updated by Jim Pingle almost 4 years ago

  • Category set to Captive Portal
  • Status changed from New to Not a Bug

There was no change in the configuration between 2.4.4-p3 and 2.4.5

The post-auth redirect URL should always have been in After authentication Redirection URL.

#9819 made it so that redirection is forced as expected when configured.

Actions #4

Updated by simon lock almost 4 years ago

Hi, Jim, I can confirm that something must have changed, possibly during the upgrade, between the two settings "Pre-authentication redirect URL" and "After authentication Redirection URL". I've always had "After authentication Redirection URL" set to "https://www.google.co.uk/" and this has always redirected the successfully connected user to this url after authentication.

However, this redirect recently stopped working. Moving the url to "Pre-authentication redirect URL" fixing the After authentication connection redirection. Which doesn't sound logical?

Actions #5

Updated by Jim Pingle almost 4 years ago

"After authentication Redirection URL" works for me when I have the client load the portal login page and login. After login, I get redirected to the URL set in the CP settings.

The change in #9819 made it so that if a client has its own redirect URL (for example, if they tried to load http://www.example.com and were redirected to the portal), that page gets loaded instead of the one set in the CP settings.

Perhaps we need a checkbox option to force the use of the post-auth redirect URL, but that wouldn't result in a 404 as described in the bug report here.

Actions

Also available in: Atom PDF