diff options
| author | Pablo Fernandez <p@f7z.io> | 2024-01-08 22:11:08 +0000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-01-08 22:11:08 +0000 |
| commit | 5868d4f67aac4fe71badd83c0ac6333d4bc4e9ac (patch) | |
| tree | d57ea02bb9accbedd01c11f9d7a3fb7aa5e32a17 | |
| parent | 7dc72f967c5cf8a225bcf911f0777948f6dd2b2a (diff) | |
Update 46.md
Co-authored-by: fiatjaf_ <fiatjaf@gmail.com>
| -rw-r--r-- | 46.md | 2 |
1 files changed, 1 insertions, 1 deletions
| @@ -71,7 +71,7 @@ The signer key will always be the key of the user who controls the signer device | |||
| 71 | ### Auth URL response | 71 | ### Auth URL response |
| 72 | A signer can reply with a `result: "auth_url", error: "<url>"`. This response can provide an easier way for the user to authorize this client to perform an action. Clients can redirect/popup this URL so the user can take an action directly on the signer backend. | 72 | A signer can reply with a `result: "auth_url", error: "<url>"`. This response can provide an easier way for the user to authorize this client to perform an action. Clients can redirect/popup this URL so the user can take an action directly on the signer backend. |
| 73 | 73 | ||
| 74 | When redirecting, the client can choose to add a `callbackUrl` query string parameter to tell the signer when to send the user after an action has been performed. | 74 | When redirecting, the client can choose to add a `callbackUrl` query string parameter to tell the signer where to send the user after an action has been performed. |
| 75 | 75 | ||
| 76 | #### Example flow: | 76 | #### Example flow: |
| 77 | 77 | ||