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

Chrome Extension blocks related origin requests (ROR) #12846

Open
1 task done
flooyo opened this issue Jan 13, 2025 · 2 comments
Open
1 task done

Chrome Extension blocks related origin requests (ROR) #12846

flooyo opened this issue Jan 13, 2025 · 2 comments
Labels
browser Browser Extension bug

Comments

@flooyo
Copy link

flooyo commented Jan 13, 2025

Steps To Reproduce

  1. Go to ror-1.glitch.me & ror-2.glitch.me to spin up the pages
  2. Install the Bitwarden Chrome extension and log in to your account
  3. Visit ror-2.glitch.me (which should make a call to ror-1.glitch.me/.well-known/webauthn)
  4. Lookup the Error message within the ServiceWorker

Expected Result

No error message, a call to the rp.id’s webauthn well-known endpoint should be made.

Actual Result

The Login into the Site is not possbile:
Console: {"lineNumber":2,"message":"[Fido2Client] 'rp.id' cannot be used with the current origin: rp.id = ror-1.glitch.me; origin = https://ror-2.glitch.me","message_level":2,"sourceIdentifier":3,"sourceURL":"chrome-extension://nngceckbapebfimnlniiiahkandclblb/background.js"}

Screenshots or Videos

image

Additional Context

No response

Operating System

macOS

Operating System Version

No response

Web Browser

Chrome

Browser Version

No response

Build Version

2024.12.4

Issue Tracking Info

  • I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
@flooyo flooyo added browser Browser Extension bug labels Jan 13, 2025
@bitwarden-bot
Copy link

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-17017

@jtodddd
Copy link

jtodddd commented Jan 13, 2025

Hi there,

Thank you for your report!

I was able to reproduce this issue, and I have flagged this to our engineering team.

If you wish to add any further information/screenshots/recordings etc., please feel free to do so at any time - our engineering team will be happy to review these.

Thanks once again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser Browser Extension bug
Projects
None yet
Development

No branches or pull requests

3 participants