Skip to content
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

"Login CISO" challenge fails when using Google login button [🐛] #1491

Closed
teodor440 opened this issue Oct 16, 2020 · 19 comments
Closed

"Login CISO" challenge fails when using Google login button [🐛] #1491

teodor440 opened this issue Oct 16, 2020 · 19 comments

Comments

@teodor440
Copy link

🐛 Bug report

Description

Logging in as CISO bypassing oauth user doesn't seem to work anymore. There is a short succesful notice when attempting to login, but afterwards I get redirected to login page and no token is issued.

🔬 Minimal Reproduction

As in the solution: make a failed login attempt as ciso@juice-sh.op with remember me box checked, refresh and login with oauth

🌳 Your Environment

Locally and heroku

Additional Information

@teodor440 teodor440 added the bug label Oct 16, 2020
@github-actions
Copy link

Thanks a lot for opening your first issue with us! 🧡 We'll get back to you shortly! ⏳ If it was a Support Request, please consider asking on the community chat next time! 💬

@bkimminich bkimminich changed the title [🐛] "Login CISO" challenge fails when using Google login button [🐛] Oct 16, 2020
@bkimminich
Copy link
Member

The workaround that was in place originally for domains not recognized by the Google App also works here, so the challenge is still solvable. Just not in the way it was originally intended to be solved with.

A more detailed analysis needs to be done to verify if/where the necessary HTTP header with the old email got lost or broken or why Google rejects the login attempts.

@bkimminich
Copy link
Member

@Rishabh-Kumar-07
Copy link

Hi! I would like to work on this. Will follow up soon with PR.

@bkimminich
Copy link
Member

Hi @Rishabh-Kumar-07, did you make any progress on this or should we consider it "up for grabs" again?

@Rishabh-Kumar-07
Copy link

Hey. I am engaged otherwise. You can mark it "up for grabs". Apology for the trouble.

@prince-7
Copy link
Contributor

I would like to work on this. Please Assign.

@prince-7
Copy link
Contributor

I have found some instances where x-user-email is used instead of X-User-Email, Is that on purpose?

@bkimminich
Copy link
Member

I don't know, but does it even make a difference for the Browser?

@prince-7
Copy link
Contributor

Maybe. Because as I looked into the issue I found that on clicking OAuth button the success message comes up shortly before redirecting back to the login page, and the request which causes this problem seems to be this one.
owasperror

@adityaofficial10
Copy link
Contributor

Hey @prince-7 @bkimminich !
If this has stalled, can i work on this?

@bkimminich
Copy link
Member

Totally, yes! 👍

@bkimminich
Copy link
Member

After almost 1 month of inactivity, this issue is now back in "who want's to give it a shot?" status! 😁

@Krshivam25
Copy link

Hi @bkimminich this issue is related to Account linking with OAuth. Which supports two industry-standard implicit and authorization code flows.

@vibhuti019
Copy link

Hi @bkimminich, I would love to give this a shot.

@mihai02t
Copy link

Hi @bkimminich. If this is stalled and nobody picked it up yet, can I work on it?

@bkimminich
Copy link
Member

I think I might have to add a new label for this issue... 😬

image

bkimminich added a commit that referenced this issue Apr 28, 2021
@bkimminich
Copy link
Member

"Fixed".

@github-actions
Copy link

This thread has been automatically locked because it has not had recent activity after it was closed. 🔒 Please open a new issue for regressions or related bugs.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants