The be compatible with the Bitwarden API, the endpoint /api/accounts/profile should also support POST requests to update your own full name.
Originally created by @DrMurx on GitHub (Jun 15, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/43
The be compatible with the Bitwarden API, the endpoint `/api/accounts/profile` should also support POST requests to update your own full name.
The masterPasswordHint should probably be parsed as Option as it might contain the hint string.
<!-- gh-comment-id:397838084 -->
@mprasil commented on GitHub (Jun 16, 2018):
Valut posts data in following format:
```
{"name":"User Name","masterPasswordHint":null,"culture":"en-US"}
```
The masterPasswordHint should probably be parsed as Option as it might contain the hint string.
I've implemented this now.
I also implemented email address change, which on the upstream server requires inputting a token sent to the new address. As we don't do email validation, I ignore any values to that field, so any value works.
<!-- gh-comment-id:397841603 -->
@dani-garcia commented on GitHub (Jun 16, 2018):
I've implemented this now.
I also implemented email address change, which on the upstream server requires inputting a token sent to the new address. As we don't do email validation, I ignore any values to that field, so any value works.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @DrMurx on GitHub (Jun 15, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/43
The be compatible with the Bitwarden API, the endpoint
/api/accounts/profileshould also support POST requests to update your own full name.@mprasil commented on GitHub (Jun 16, 2018):
Valut posts data in following format:
The masterPasswordHint should probably be parsed as Option as it might contain the hint string.
@dani-garcia commented on GitHub (Jun 16, 2018):
I've implemented this now.
I also implemented email address change, which on the upstream server requires inputting a token sent to the new address. As we don't do email validation, I ignore any values to that field, so any value works.