-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doubts about login/logout redir behaviour #236
Comments
I found this: https://github.com/OWASP/CheatSheetSeries/blob/master/cheatsheets/Unvalidated_Redirects_and_Forwards_Cheat_Sheet.md.
|
Hi again @frederikhors. I'm actually not sure that that's a supported way of using authboss (to redirect outside it's primary domain). It is definitely wrong to allow a full URL in the redir query parameter. Sounds like a special feature request you'd have to patch in yourself for your use case :( |
If you wanted to make it a real feature in Authboss it'd have to use the trusted URLs as shown in the notes you pasted. |
Issue opened for the creation of a wiki page that summarizes the doubts and problems for newbies (#210).
I have two doubts about the
redir
behaviour of authboss.SCENARIO:
I have two sides:
Many times I need to disconnect the user so I redirect it from let's say
client.mysite.com/teams/1
tobackend.mysite.com/authboss/logout?redir=/teams/1
.It doesn't work because
authboss
detects unauthorized account (invalidated from client side) and redirects tobackend.mysite.com/authboss/login?redir=%2F
and I loose myredir
info.DOUBT 1:
Can we pass
redir
info from/logout
to/login
?DOUBT 2:
Even if I use
/login?redir=/teams/1
I read some time ago that it is wrong - from a security point of view - to enter complete URLs in theredir
info such as:backend.mysite.com/authboss/login?redir=https://client.mysite.com/teams/1
.I know authboss automagically adds the
backend.mysite.com/
part after login and before redirect toredir
.Is there a way to change this initial part (eg. with
https://client.mysite.com/
)?Is
Config.Paths.AuthLoginOK
involved here in some way?The text was updated successfully, but these errors were encountered: