-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Description
Steps To Reproduce
- Create a group.
- Create a collection.
- Use the API or the Web Vault to add the group to the collection with "manage" permission.
Expected Result
Response status 200, collection is updated.
Actual Result
Response status 500, unhandled server exception - collection is still updated!
fail: Bit.Api.Utilities.ExceptionHandlerFilterAttribute[0]
=> SpanId:e3e6d7d32b55e7a0, TraceId:79d323659e2c99718ec674f139e9891d, ParentId:0000000000000000 => ConnectionId:0HN76SIKD24L3 => RequestPath:/public/collections/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx RequestId:0HN76SIKD24L3:00000001 => Bit.Api.Public.Controllers.CollectionsController.Put (Api)
An exception was thrown while attempting to evaluate a LINQ query parameter expression. See the inner exception for more information. To show additional information call 'DbContextOptionsBuilder.EnableSensitiveDataLogging'.
System.InvalidOperationException: An exception was thrown while attempting to evaluate a LINQ query parameter expression. See the inner exception for more information. To show additional information call 'DbContextOptionsBuilder.EnableSensitiveDataLogging'.
---> System.ArgumentNullException: Value cannot be null. (Parameter 'source')
Screenshots or Videos
No response
Additional Context
I'm working on importing content from our previous PW management solution to Bitwarden. As part of that, I'm creating groups and collections via the API. I can fire all my requests and just ignore that I'm getting 500 errors, since it actually does the thing I need it to do.
It's still clearly incorrect behaviour.
This is basically the payload I send:
"externalId": "my-reference",
"groups": [
{
"id": xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx,
"readOnly": false,
"hidePasswords": false,
"manage": true
}
]
Githash Version
8a02b49-dirty
Environment Details
Unified deployment on an OpenShift cluster.
Database Image
No response
Issue-Link
Issue Tracking Info
- I understand that work is tracked outside of Github. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.