aboutsummaryrefslogtreecommitdiffstats
path: root/src/api.rs
Commit message (Collapse)AuthorAgeFilesLines
* don't delete custom fields when editing passwordsJesse Luehrs2024-04-201-11/+83
|
* remove previous manual setting of user agent during loginJesse Luehrs2024-04-201-6/+2
|
* set a user agent in our api clientJesse Luehrs2024-04-201-13/+19
|
* clippy and fmtJesse Luehrs2024-01-011-4/+4
|
* Merge pull request #151 from Ty3uK/bugfix/login-errorJesse Luehrs2024-01-011-0/+4
|\ | | | | Pass `User-Agent` header to prevent login from returning 400
| * Pass `User-Agent` header to prevent login from returning 400Maksim Karelov2023-12-201-0/+4
| | | | | | | | Fixes #145
* | implements ability to edit notesTin Lai2023-09-211-1/+6
|/ | | | Signed-off-by: Tin Lai <oscar@tinyiu.com>
* improve error reporting when login or register failJesse Luehrs2023-07-181-2/+26
|
* add yubikey supporttroyready2023-06-171-0/+2
| | | | | This is all that's needed to support Yubikey hardware tokens in OTP mode (https://developers.yubico.com/OTP/)
* clippy, fmt, etcJesse Luehrs2023-03-251-102/+109
|
* Switch kdf type to enumBernd Schoolmann2023-03-261-2/+93
|
* Implement argon2 kdfBernd Schoolmann2023-03-261-2/+8
|
* Add support for 2FA-method 'Email'.René 'Necoro' Neumann2023-03-191-0/+25
| | | | | | | | | Generalize the `two_factor` function to allow for different Providers. The `login` function now holds a list of supported providers that it tests in turn. The list should probably adhere to https://bitwarden.com/help/setup-two-step-login/#using-multiple-methods. Closes #90.
* more clippy cleanupsJesse Luehrs2023-02-181-3/+0
|
* refactor client cert handlingJesse Luehrs2023-02-181-23/+38
|
* bump depsJesse Luehrs2023-02-181-2/+2
|
* clippyJesse Luehrs2023-02-181-22/+31
|
* support for client certificatesFilipe Pina2022-05-261-6/+23
|
* update to support camel case api namesJesse Luehrs2022-02-101-64/+64
| | | | | official bitwarden server just updated to this, but vaultwarden still uses pascal case
* clippyJesse Luehrs2021-12-151-37/+41
|
* add a useful error message if registration is requiredJesse Luehrs2021-10-271-0/+3
|
* add a separate "register" command to log in with api keysJesse Luehrs2021-10-271-42/+49
|
* use a persistent device idJesse Luehrs2021-10-271-3/+2
|
* start working on apikey authenticationJesse Luehrs2021-10-271-15/+54
| | | | | | | | | | not entirely working yet, because api keys aren't allowed to use the offline_access scope which provides access to the oauth refresh token. we will probably need to move to using stable device identifiers (should be able to generate one when the config is first created) and move this logic to a separate "rbw register" command which just does an apikey login but doesn't try to store any data, and then use the normal login flow after that
* add the auth-email header when authenticatingJesse Luehrs2021-10-271-0/+4
| | | | | required by new version of the official bitwarden server, see https://github.com/bitwarden/jslib/pull/394
* clippyJesse Luehrs2021-10-271-1/+1
|
* clippyJesse Luehrs2021-07-051-1/+1
|
* TwoFactorProviderType: Allow WebAuthnSarah Brofeldt2021-05-311-0/+3
| | | | | Only allows deserialization for the new provider. See https://github.com/bitwarden/server/pull/903
* Don't choke on empty passwords in the historyLionel Flandrin2021-04-011-4/+8
| | | | Fixes #50
* switch to thiserrorJesse Luehrs2021-03-061-10/+10
|
* persist uri match type when editingJesse Luehrs2021-02-211-3/+47
|
* clippyJesse Luehrs2021-02-191-1/+1
|
* allow TwoFactorType to be provided as an integer or stringJesse Luehrs2020-12-021-14/+67
| | | | | bitwarden-rs still provides it as an integer, but bitwarden.com now provides it as a string
* use a better device name when logging inJesse Luehrs2020-10-131-1/+1
|
* clippyJesse Luehrs2020-10-121-3/+3
|
* do not display deleted itemsEmmanuel Garette2020-10-121-0/+5
|
* add totp, uris, and custom fields to --full outputJesse Luehrs2020-07-251-0/+31
|
* clippyJesse Luehrs2020-07-111-1/+1
|
* display the server's error message for incorrect passwordJesse Luehrs2020-05-281-19/+22
|
* add authenticator 2fa supportJesse Luehrs2020-05-281-4/+56
|
* parse login error correctlyJesse Luehrs2020-05-271-9/+45
|
* handle uri entries with no uri setJesse Luehrs2020-05-241-4/+12
| | | | | | apparently this can happen if you create the uri entry but then delete the contents of the uri afterward? probably also in other edge case scenarios
* better error messages when parsing a server messageJesse Luehrs2020-05-231-14/+12
|
* don't expect the refresh token response to have a keyJesse Luehrs2020-05-171-2/+0
| | | | the official server doesn't do this, and i don't use it anyway
* maintain folder and uris when editing an entryJesse Luehrs2020-05-031-7/+34
|
* fix editing organization entriesJesse Luehrs2020-05-031-0/+4
|
* start adding support for different entry typesJesse Luehrs2020-05-031-67/+306
|
* remove some old debuggingJesse Luehrs2020-05-031-6/+3
|
* also store org keys in the local dbJesse Luehrs2020-05-031-1/+23
|
* save the private key to the local dbJesse Luehrs2020-05-031-2/+8
|
generated by cgit v1.2.3-54-g00ecf (git 2.45.0) at 2024-05-17 07:52:15 +0000