Closed OdyX closed 3 years ago
I see the point, but the search for the user must be based on whatever criterion the user want (email, id, or name). Basically, your patch is good, i ll integrate the idea.
Afterall, i came up with the same patch, so i merged yours, congrats ! :tada:
First, thanks a lot for this quite excellent Bitwarden Python API implementation, it spared me insane lots of rewriting!
While implementing an automated synchronization tool between our employee directory and a (1.22.2) Vaultwarden server, I stumbled upon the requirement of the server private key to confirm users in organizations.
But as far as I could quick patch, I can correctly confirm users by going this way:
… with confirm_invitation patched as follows:
In other words, it seems that
confirm_invitation
relies onget_users
having access to/admin/users
to "just" get the userId; but that's now directly accessible in organization access lists.Feel free to integrate any variation of my patch. Alternatively, I'd be happy to provide a more precise patch if you'd be interested in shipping something like that! Guidance might be needed to avoid wreaking havoc!