bitwarden/passwordless-docs

passwordless-docs's Issues

Support for devicePubKey extension of WebAuthn

Does passwordless.dev support the devicePubKey extension of webauthn? I don't see any information about it in the documentation, and I don't see any implementation of it in source code (after cursory search).

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

• [deps]: Lock file maintenance

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• [deps]: Pin dependencies (@passwordlessdev/passwordless-client, check-md, eslint, eslint-config-prettier, eslint-plugin-vue, prettier, prettier-plugin-organize-imports, vuepress, vuepress-plugin-check-md, vuepress-plugin-code-switcher)
• [deps]: Update vuepress-plugin-code-switcher to v2

Detected dependencies

github-actions

.github/workflows/main.yml

• actions/checkout v4.1.1@b4ffde65f46336ab88eb53be808477a3936bae11
• actions/setup-node v4.0.1@b39b52d1213e96004bfcb1c61a8a6fa8ab84f3e8

npm

package.json

• @passwordlessdev/passwordless-client ^1.1.2
• vuepress-plugin-code-switcher ^1.1.0
• eslint ^8.50.0
• eslint-config-prettier ^9.0.0
• eslint-plugin-vue ^9.17.0
• prettier ^3.0.3
• prettier-plugin-organize-imports ^3.2.3
• vuepress ^1.9.10
• vuepress-plugin-check-md ^0.0.3
• check-md ^1.0.2

---

• Check this box to trigger a request for Renovate to run again on this repository

Confusing recursive definition

https://docs.passwordless.dev/guide/concepts.html#discoverable-credential

"Discoverable Credential is a passkey" but also "Passkeys are an example of Discoverable Credentials"?

Navigating to a specific header by ID seems broken

For example, open the following link: https://docs.passwordless.dev/guide/concepts.html#discoverable-credential

You'll see that the browser scrubs the #... part upon page load and stays at the beginning of the page, instead of navigating to the correct header.

Standardize on API endpoints in examples

Currently, the docs are a bit misaligned on API routes when it comes to user-implemented backend endpoints.

For example, docs for the JS client (frontend) use /create-token and /signin: https://docs.passwordless.dev/guide/frontend/javascript.html#register

While the docs for the .NET client (backend) use /create-token and /verify-signin: https://docs.passwordless.dev/guide/backend/dotnet.html

Additionally, docs for the JS client assume that /create-token returns the raw token (string) directly: https://docs.passwordless.dev/guide/frontend/javascript.html#register

While the docs for the .NET client return the token as part of a JSON object: https://docs.passwordless.dev/guide/backend/dotnet.html

This inconsistency can lead to silly bugs and it would be nice to standardize on some convention.

Misspelled "Proprety" in Credential section of concepts.md

Misspelled "Proprety" in Credential section of concepts.md