POST /api/ciphers/create application/json; charset=utf-8:
=> Matched: POST /api/ciphers/<uuid>
=> Error: Couldn't parse JSON body: Error("missing field `Type`", line: 1, column: 568)
=> Outcome: Failure
=> Warning: Responding with 400 Bad Request catcher.
=> Response succeeded.
When trying to add an item to a collection from the desktop app, from the web vault it works fine.
Originally created by @titansmc on GitHub (Nov 15, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/253
Hi,
I have this error
````
POST /api/ciphers/create application/json; charset=utf-8:
=> Matched: POST /api/ciphers/<uuid>
=> Error: Couldn't parse JSON body: Error("missing field `Type`", line: 1, column: 568)
=> Outcome: Failure
=> Warning: Responding with 400 Bad Request catcher.
=> Response succeeded.
````
When trying to add an item to a collection from the desktop app, from the web vault it works fine.
@mprasil This seems different, the post is going to /api/ciphers/create, we might need to create a new alias to POST /api/ciphers/
<!-- gh-comment-id:439076889 -->
@dani-garcia commented on GitHub (Nov 15, 2018):
@mprasil This seems different, the post is going to `/api/ciphers/create`, we might need to create a new alias to `POST /api/ciphers/`
Yeah, that's true. I assume this is already going to be part of vault 2.6.0 once that is released. Hopefully should be easy fix.
<!-- gh-comment-id:439081453 -->
@mprasil commented on GitHub (Nov 15, 2018):
Yeah, that's true. I assume this is already going to be part of vault `2.6.0` once that is released. Hopefully should be easy fix.
For anyone affected by this. A simple workaround is to add the item to your local vault and then share the item to organization.
<!-- gh-comment-id:439083921 -->
@mprasil commented on GitHub (Nov 15, 2018):
For anyone affected by this. A simple workaround is to add the item to your local vault and then share the item to organization.
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 @titansmc on GitHub (Nov 15, 2018).
Original GitHub issue: https://github.com/dani-garcia/vaultwarden/issues/253
Hi,
I have this error
When trying to add an item to a collection from the desktop app, from the web vault it works fine.
@mprasil commented on GitHub (Nov 15, 2018):
Are you using the latest image. It should be fixed there.
@dani-garcia commented on GitHub (Nov 15, 2018):
@mprasil This seems different, the post is going to
/api/ciphers/create, we might need to create a new alias toPOST /api/ciphers/@mprasil commented on GitHub (Nov 15, 2018):
Yeah, that's true. I assume this is already going to be part of vault
2.6.0once that is released. Hopefully should be easy fix.@mprasil commented on GitHub (Nov 15, 2018):
For anyone affected by this. A simple workaround is to add the item to your local vault and then share the item to organization.
@dani-garcia commented on GitHub (Nov 19, 2018):
This should be fixed now