Odd situation of showing a login page when already logged in #1

New issue

Closed

opened 2024-01-23 09:12:34 +00:00 by edward · 1 comment

edward commented

2024-01-23 09:12:34 +00:00

Owner

Start flask development server for service on http://localhost:5000/
Service looks for a UniAuth cookie and doesn't find it, so redirects to https://edwardbetts.com/UniAuth/login
User is already authenticated via UniAuth, the cookie lives on 4angle.com
If the user re-authenticates they get redirected to http://localhost:5000/ which redirects them back to the login page

Need to show a message on the UniAuth page explaining the problem.

What if the service requesting the login is responsible for setting the cookie?

The requesting service could look for a login cookie, when it doesn't find it redirect the user to UniAuth. After login UniAuth can redirect with the auth_token as a URL parameter and the local service can set the auth cookie.

1. Start flask development server for service on http://localhost:5000/ 2. Service looks for a UniAuth cookie and doesn't find it, so redirects to https://edwardbetts.com/UniAuth/login 3. User is already authenticated via UniAuth, the cookie lives on 4angle.com 4. If the user re-authenticates they get redirected to http://localhost:5000/ which redirects them back to the login page Need to show a message on the UniAuth page explaining the problem. What if the service requesting the login is responsible for setting the cookie? The requesting service could look for a login cookie, when it doesn't find it redirect the user to UniAuth. After login UniAuth can redirect with the auth_token as a URL parameter and the local service can set the auth cookie.

edward commented

2024-02-15 17:54:52 +00:00

Author

Owner

Current design assumes all applications run on the same host as UniAuth. This isn't necessarily true. We need a design that allows the application to run on a different host to the authentication provider.