DuckDuckGo not working on Self-Hosted environments (CORS Protected like FireFox)

[BlackDex]

Steps To Reproduce

1. Go to a self-hosted environment using some private hostname, not something with bitwarden.com
2. Go to Tools > Generator > Forwarded Email Alias
3. Select DuckDuckGo, just enter random string, or an actual correct API key of course.
4. Try to generate.

It will respond with a CORS error.

Expected Result

Either:

1. A valid response from DuckDuckGo
2. DuckDuckGo not available for self-hosted environments, the same currently is for the FireFox Relay.

Actual Result

DuckDuckGo option is available but not working.

Screenshots or Videos

Additional Context

I also tried this via cURL by using the the request send by vault.bitwarden.com, which does work, and if i change it to anything else, it will not respond with the needed headers. So it looks like DuckDuckGo is CORS protected same as FireFox.

Operating System

Windows, macOS, Linux

Operating System Version

No response

Web Browser

Chrome, Firefox

Browser Version

No response

Build Version

2022.10.0

[Hinton]

Thanks for the report.

This should most likely have been removed from self-hosted. Waiting to hear back from some colleagues first to confirm.

[BlackDex]

Though, I find it a bit strange actually. The Mobile client allows FireFox to work, but the web-vault for self-hosted env's has it removed. If i try to access the API manually, it seems to at least respond with an invalid token message.

The only thing which breaks is the CORS part by first sending an OPTIONS call which fails, for some reason, but if I manually send a POST it works.

I haven't worked with the whole CORS backend/frontend that much, so I'm not sure how this should work exactly.

[Hinton]

That's how CORS works. The browser sends an OPTION call to check if the website allows clients from another website to make requests. Which protects against potentially stealing sensitive information. https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

[MuadDibIII]

Hello all, I created the bug report closed by justindbaur.

Just to check if I understood correctly, will the feature be implemented or just removed from the self-hosted servers?

I'm actually choosing an alias service, and this info can help with my choice...

[Hinton]

It will be disabled for the web vault on self-hosted instances, but it will still be available on all the other clients.

[MuadDibIII]

Ok, thank you