you there?
Are you a developer?
It's a little inconsistent with how other items are treated, but I think
send was considered different enough that it was better to put it all related commands one place and keep them separate from other items
is there a way to disable the update prompt in bitwarden desktop?
1 reply
I have to manually downgrade after I accidentally upgrade every time due to the ctrl-w bug
I have 6 input fields on a user account page, I can’t seem to determine how bitwarden chooses what to autofill. I have 2 inputs “username” and “current-password”, but autofill wants to fill “email” and “alias”, even when they arenot within the form tag. Bitwarden also fills more that 2 inputs in some cases.
Not sure what I am missing, please help!
Good Morning bitwarden team, I am looking into contributing and found this issue labeled "Good first issue". bitwarden/server#852 I think I have the necessary code changes, but I am looking to test it locally. I followed the SETUP.md and have the Api and Identity projects running. The issue I am running into is the authorization method. It looks like I need to setup a Client ID and Client Secret. How would I go about setting that up? Is it the installation ID and Key I used during the setup? If there is some documentation for getting that setup, feel free to point me in that direction as well. Thanks!
Hi @BashfulBandit, you can follow the instructions here to find your api key (client ID + client secret): https://bitwarden.com/help/article/public-api/
You'll need the web vault client set up and pointing to your local server as well, if you haven't already done that
Hey @eliykat Thanks for that information! I did realize after asking originally that I needed to run the web vault locally. The issue I am running into is it won't let me create an organization for the account I made if "selfhosted": true. When I set "selfhosted" to false, then the API and Identity services won't run. I may be missing something, but is there a way around this? The only client ID and client secret I am able to access is for a User, but the endpoint I am wanting to test requires an organization.
Yes, unfortunately those are paid features and we have no way of giving out organization subscriptions just for development/testing purposes. It's a bit of a blocker when it comes to community contributions. But I can see that you've figured it out and submitted a PR, so I'll check it out :)
Hi @marpo60, I don't believe we have any options for that at the moment, but you can make a feature request on our community forums: http://community.bitwarden.com
Hey folks. I've just got bitwarden working behind traefik. I am able to create new users and log in and see the admin console, however, I have run into an error with the "portal" service while trying to set up OIDC SSO. After I fill out the form on bitwarden with my sso information and hit save the portal service fails with an error message saying
2021-08-21 02:26:05.890 +00:00 [Error] An exception was thrown while deserializing the token.
Microsoft.AspNetCore.Antiforgery.AntiforgeryValidationException: The antiforgery token could not be decrypted.
---> System.Security.Cryptography.CryptographicException: The key {some-real-key} was not found in the key ring.
So if you have an alt account you barely use, the autofill will pretty much default to your 'preferred' (i.e. most recently used) account
I've cloned and run the web repo and can access the vault in my browser fine. But, I'm trying two things. 1. Connecting the frontend to the production Bitwarden servers. 2. Connecting the frontend to my own vaultwarden instance (behind a reverse-proxy). In either case, changing the ENV variable (when running npm) does not change the baseURL that requests are made from. Thus I'm getting these errors in the browser terminal (see image).
Yes. I've tried
ENV=production npm run build:oss:watch as per the docs as well.
when you first run the npm script, you should see a printout of the loaded config, can you confirm it's loading your proxy settings correctly?
But if we ignore my vaultwarden setup (since that might come with other issues), just connecting to bitwarden cloud is not working.
As per the Github README
our devops team didn't like
production since that's ambiguous between cloud and self-hosted users
The baseURL for all requests are still
localhost:8080
@MGibson1 I think we forgot to setup the proper proxies in production after https://github.com/bitwarden/web/pull/1151/files