dwbit
December 30, 2022, 1:16pm
302
Hey @viktor Bitwarden send functionality will be expanded so that you’ll be able to send a vault item and have someone add it to their own vault, including those outside of the organization.
18 Likes
tomtom
May 10, 2023, 12:33pm
325
It seems like the roadmap got updated since my last visit. What does „Account Security with Passkeys“ mean?
Could it be something like 1Password plans? (Which is something I‘d reeeeeally like to see.)
2 Likes
dwbit
May 10, 2023, 12:43pm
326
Hey there! Bitwarden is working on additional passwordless options to access your Bitwarden account
3 Likes
JDD
May 12, 2023, 12:52am
328
Glad to hear. Live the transparency. My hope is that this statement indicates working toward replacement of master password with passkeys instead of just adding another option. While I understand this may be a multi step process, I’m hoping it’s building toward this
BW put out a passkey demo on YT
1 Like
Now a 2nd video showing a demo of signing in to BW with a Passkey.
I note
there is an optional 2nd step to enable encryption. What would be the point of creating a Passkey without encryption?
the version
3 Likes
Is there any news when Log in with device (Log in with Device | Bitwarden Help Center ) will be available for self hosted environments?
Edit : Just found the PRs by myself:
bitwarden:master ← bitwarden:PM-1101-passwordless-on-self-hosted
opened 08:48PM - 12 May 23 UTC
## Type of change
```
- [ ] Bug fix
- [X] New feature development
- [ … ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other
```
## Objective
We currently do not allow self-hosted customers to use Login with Device. This is due to our notifications not working on self-hosted. We have addressed this with https://github.com/bitwarden/server/pull/2934. This change is to remove the client-side checks that prevented the button from displaying.
## Code changes
- **/desktop/src/auth/login/login.component.ts** Replaced `checkSelfHosted()` checks with an explicit `getLoginWithDevice()` call, as that is the only remaining functionality in the `checkSelfHosted()` method
- **/libs/angular/src/auth/components/login.component.ts** Removed check for self-hosted from `getLoginWithDevice()`
- **selfhosted.json** Changed `showPasswordless` to `true` for self-hosted web client.
## Before you submit
- Please add **unit tests** where it makes sense to do so (encouraged but not required)
- If this change requires a **documentation update** - notify the documentation team
- If this change has particular **deployment requirements** - notify the DevOps team
- Ensure that all UI additions follow [WCAG AA requirements](https://contributing.bitwarden.com/contributing/accessibility/)
bitwarden:master ← bitwarden:PM-1101-passwordless-on-self-hosted
opened 08:45PM - 12 May 23 UTC
## Type of change
```
- [ ] Bug fix
- [X] New feature development
- [ … ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other
```
## Objective
Self-hosted customers cannot use Login with Device, as they don't receive the approval notification on their requesting device.
## Code changes
**SendController.cs:** Injected the `AnonymousHubContext` into the `Send` method on the Notifications Service so that self-hosted customers receive notifications. It was being passed in as `null` to the `HubHelper` which resulted in a null reference exception when trying to send the message. The equivalent initialization for the `AzureQueueHostedService` does initialize it correctly, which is why cloud-hosted customers have no issues.
**nginx-config.hbs / NginxConfig.hbs:** Added configuration for anonymous hub to nginx configuration for self-hosted.
**HubHelpers.cs:** Deserialized the message contents using the `deserializationOptions` used at all other places in the method, to ensure that we are case-insensitive in our deserialization.
## Before you submit
- Please check for formatting errors (`dotnet format --verify-no-changes`) (required)
- If making database changes - make sure you also update Entity Framework queries and/or migrations
- Please add **unit tests** where it makes sense to do so (encouraged but not required)
- If this change requires a **documentation update** - notify the documentation team
- If this change has particular **deployment requirements** - notify the DevOps team
Seems they just have missed the recent may release
Nothing gets past you! Keep an eye out for our next release
Researching
Planned
In Progress
Implemented (for a comprehensive list, visit the release notes page)
2023.4.2
