Adding item to organization fails #121

Closed
opened 2026-02-04 17:09:13 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @ottidmes on GitHub (Nov 6, 2018).

When I try to add an item to an organization I get a similar error as mentioned in issues #37 and #178. The error occurs under the latest commit at this time: 8f5bfe7938.

The logs:

GET /api/organizations/8a9b9e44-bae1-4ebe-a6d5-648dbf234368/collections application/json:
    => Matched: GET /api/organizations/<org_id>/collections
    => Outcome: Success
    => Response succeeded.
GET /api/ciphers/organization-details?organizationId=8a9b9e44-bae1-4ebe-a6d5-648dbf234368 application/json:
    => Matched: GET /api/ciphers/organization-details?<data>
    => Outcome: Success
    => Response succeeded.
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: 366)
    => Outcome: Failure
    => Warning: Responding with 400 Bad Request catcher.
    => Response succeeded.
GET /images/totp-countdown.png:
    => Matched: GET /<p..>
    => Outcome: Success
    => Response succeeded.
POST /api/ciphers/admin application/json; charset=utf-8:
    => Matched: POST /api/ciphers/admin
    => Error: Couldn't parse JSON body: Error("missing field `Type`", line: 1, column: 530)
    => Outcome: Failure
    => Warning: Responding with 400 Bad Request catcher.
    => Response succeeded.

Request payload POST /api/ciphers/admin:

{"cipher":{"type":1,"folderId":null,"organizationId":"8a9b9e44-bae1-4ebe-a6d5-648dbf234368","name":"2.A55Mq1GreJLU1atXowzwWw==|mo8HMh4C9zELT8MyEXBNWw==|HrghoZxvaq8XdpS5VqE0Kgo/VJzYCDTkFAs4FllBuOU=","notes":null,"favorite":false,"login":{"uris":null,"username":"2.j2ldJh00cPwD58vUJAYDVw==|SbzxBu8XU9+6C0FDqHHckg==|xBCmRmDluYJ3RwINlH+p+QsRSD+4CGo2dZfBQO5yxq4=","password":"2.+QwcssOdpOBFztyFx74GFw==|btV/2pgBQy86/7Ah7k0uzQ==|P0bESvm7yzPPZW0NaALMeJ/AyLTAnIDdmEQi0ocLLko=","passwordRevisionDate":null,"totp":null}},"collectionIds":[]}
Originally created by @ottidmes on GitHub (Nov 6, 2018). When I try to add an item to an organization I get a similar error as mentioned in issues #37 and #178. The error occurs under the latest commit at this time: 8f5bfe7938b9037fb802c0811b28f2575f3b0e89. The logs: ``` GET /api/organizations/8a9b9e44-bae1-4ebe-a6d5-648dbf234368/collections application/json: => Matched: GET /api/organizations/<org_id>/collections => Outcome: Success => Response succeeded. GET /api/ciphers/organization-details?organizationId=8a9b9e44-bae1-4ebe-a6d5-648dbf234368 application/json: => Matched: GET /api/ciphers/organization-details?<data> => Outcome: Success => Response succeeded. 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: 366) => Outcome: Failure => Warning: Responding with 400 Bad Request catcher. => Response succeeded. GET /images/totp-countdown.png: => Matched: GET /<p..> => Outcome: Success => Response succeeded. POST /api/ciphers/admin application/json; charset=utf-8: => Matched: POST /api/ciphers/admin => Error: Couldn't parse JSON body: Error("missing field `Type`", line: 1, column: 530) => Outcome: Failure => Warning: Responding with 400 Bad Request catcher. => Response succeeded. ``` Request payload `POST /api/ciphers/admin`: ``` {"cipher":{"type":1,"folderId":null,"organizationId":"8a9b9e44-bae1-4ebe-a6d5-648dbf234368","name":"2.A55Mq1GreJLU1atXowzwWw==|mo8HMh4C9zELT8MyEXBNWw==|HrghoZxvaq8XdpS5VqE0Kgo/VJzYCDTkFAs4FllBuOU=","notes":null,"favorite":false,"login":{"uris":null,"username":"2.j2ldJh00cPwD58vUJAYDVw==|SbzxBu8XU9+6C0FDqHHckg==|xBCmRmDluYJ3RwINlH+p+QsRSD+4CGo2dZfBQO5yxq4=","password":"2.+QwcssOdpOBFztyFx74GFw==|btV/2pgBQy86/7Ah7k0uzQ==|P0bESvm7yzPPZW0NaALMeJ/AyLTAnIDdmEQi0ocLLko=","passwordRevisionDate":null,"totp":null}},"collectionIds":[]} ```
Author
Owner

@ottidmes commented on GitHub (Nov 6, 2018):

I was using the master build of the Bitwarden Web Vault, after changing it to the commit of version 2.4.0, it worked again.

@ottidmes commented on GitHub (Nov 6, 2018): I was using the master build of the Bitwarden Web Vault, after changing it to the commit of version 2.4.0, it worked again.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/vaultwarden#121