From ccd57c57c8250d11322b61973d98bc0ec7993db2 Mon Sep 17 00:00:00 2001
From: Olivia Thet
Date: Wed, 29 Nov 2023 10:38:28 -0500
Subject: [PATCH] adjust more image sizes
---
docs/getting-started/email-recovery.md | 2 +-
docs/integration-guides/export-wallets.md | 18 +++++++++++++++---
docs/passkeys/options.md | 4 +---
3 files changed, 17 insertions(+), 7 deletions(-)
diff --git a/docs/getting-started/email-recovery.md b/docs/getting-started/email-recovery.md
index d4fa9e7..4a0802a 100644
--- a/docs/getting-started/email-recovery.md
+++ b/docs/getting-started/email-recovery.md
@@ -42,7 +42,7 @@ Authorization for email recovery is based on our usual activity authorization: o
diff --git a/docs/integration-guides/export-wallets.md b/docs/integration-guides/export-wallets.md
index a15c61d..ff1c9c6 100644
--- a/docs/integration-guides/export-wallets.md
+++ b/docs/integration-guides/export-wallets.md
@@ -28,7 +28,11 @@ In the rest of this guide we'll assume you are using these helpers.
Here's a diagram summarizing the wallet export flow step-by-step ([direct link](/img/wallet_export_steps.png)):
-
+
Let's review these steps in detail:
@@ -75,7 +79,11 @@ Let's review these steps in detail:
Export is complete! The iframe now displays a numbered 3-column grid of words that form the mnemonic, directly to your end user.
-
+
The exported wallet will remain stored within Turnkey’s infrastructure. In your Turnkey dashboard, the exported user Wallet will be flagged as “Exported”.
@@ -113,7 +121,11 @@ It works by anchoring export in a **target encryption key** (TEK). This target e
The following diagram summarizes the flow:
-
+
The public part of this key pair is passed as a parameter inside of a signed `EXPORT_WALLET` or `EXPORT_PRIVATE_KEY` activity.
diff --git a/docs/passkeys/options.md b/docs/passkeys/options.md
index 6f83716..80f0366 100644
--- a/docs/passkeys/options.md
+++ b/docs/passkeys/options.md
@@ -26,8 +26,6 @@ Number of seconds before "giving up". The browser will simply show a timeout pop
alt="authenticatorAttachment unspecified"
style={{ width: 360 }} />
-
-
This UI isn't very helpful, so we recommend making the timeout long (5 minutes). The less your users see this, the better.
@@ -65,7 +63,7 @@ Turnkey currently supports P256 only. In the near future Turnkey will support RS
The `user` field has three sub-fields:
- `id`: also known as "user handle", isn't visible to the end-user. We **strongly recommend setting this to a random value** (e.g. `const id = new Uint8Array(32); crypto.getRandomValues(id)`) to make sure a new passkey is created. Be aware: **if you accidentally set this value to an existing user handle, the corresponding passkey will be overridden!**. [This section of spec](https://www.w3.org/TR/webauthn-2/#dictionary-user-credential-params) is clear on the matter: "the user handle ought not be a constant value across different accounts, even for non-discoverable credentials".
-- `name`: this will show up in the passkey list modal (see screenshot below). We recommend setting this to something the user will recognize: their email, the name of your app, or potentially leave this up to the user:
+- `name`: this will show up in the passkey list modal (see screenshot below). We recommend setting this to something the user will recognize: their email, the name of your app, or potentially leave this up to the user: