You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -202,7 +202,7 @@ Bind tokens to a key your server holds ([RFC 9449](https://www.rfc-editor.org/rf
202
202
203
203
### 10. Passwordless Authentication
204
204
205
-
Sign users in with a one-time code sent by email or SMS, or with a magic link sent by email, via [Auth0 embedded passwordless login](https://auth0.com/docs/authenticate/passwordless/implement-login/embedded-login/relevant-api-endpoints). OTP verification and the magic-link callback each establish a server-side session like every other login path. For prerequisites, both flows, custom scopes/audiences, organizations, step-up MFA, and error handling, see [examples/Passwordless.md](examples/Passwordless.md).
205
+
Sign users in with a one-time code sent by email or SMS, or with a magic link sent by email, via [Auth0 embedded passwordless login](https://auth0.com/docs/authenticate/passwordless/implement-login/embedded-login/relevant-api-endpoints). OTP verification and the magic-link callback each establish a server-side session like every other login path. For prerequisites, both flows, custom scopes/audiences, step-up MFA, and error handling, see [examples/Passwordless.md](examples/Passwordless.md).
Copy file name to clipboardExpand all lines: examples/Passwordless.md
-28Lines changed: 0 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,7 +17,6 @@ Passwordless lets users sign in with a one-time code sent by email or SMS, or wi
17
17
-[3. Email magic link](#3-email-magic-link)
18
18
-[4. Custom scopes and audiences](#4-custom-scopes-and-audiences)
19
19
-[5. Forwarding the end-user IP](#5-forwarding-the-end-user-ip)
20
-
-[6. Organizations (magic link only)](#6-organizations-magic-link-only)
21
20
-[Completing MFA during passwordless login](#completing-mfa-during-passwordless-login)
22
21
-[Error Handling](#error-handling)
23
22
@@ -254,32 +253,6 @@ result = await server_client.passwordless.verify(
254
253
> [!WARNING]
255
254
> Only forward a trusted, normalized end-user IP from your edge/proxy layer. Do not blindly copy arbitrary client-supplied headers into `client_ip`.
256
255
257
-
## 6. Organizations (magic link only)
258
-
259
-
Magic links can carry an organization through `authParams`; the SDK stores the expected organization in the transaction and validates the claims returned by the callback.
If the callback's ID token does not include a matching organization claim, verification fails before a session is persisted, raising `OrganizationTokenValidationError`.
273
-
274
-
> [!NOTE]
275
-
> `VerifyPasswordlessOtpOptions` (the OTP `verify()` path) has no `organization`
276
-
> field. Auth0 does not attach an organization claim to tokens issued by the
277
-
> passwordless-OTP grant, so there is nothing for the SDK to validate against
278
-
> — an OTP flow that needs organization-scoped login should use magic link
279
-
> instead. The model rejects unknown fields, so passing `organization` to
280
-
> `verify()` raises a pydantic `ValidationError` rather than being silently
281
-
> dropped.
282
-
283
256
## Completing MFA during passwordless login
284
257
285
258
Auth0 can require MFA during passwordless OTP verification. In that case, the SDK raises `MfaRequiredError` before it creates a session. Complete the MFA challenge with `server_client.mfa`, then persist the returned tokens according to your framework's session integration.
0 commit comments