feat: [AIDX-130] add notification channel settings content updates #189
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
priley86
commented
Oct 28, 2025
| - **User's email verification status**: if the user's email is not verified, we assume sending emails to an unverified email address is not desired, and the request will be rejected. | ||
|
|
||
| You can read more about the notification channel selection in the [Configure Client-Initiated Backchannel Authentication](https://auth0.com/docs/get-started/applications/configure-client-initiated-backchannel-authentication) documentation. | ||
|
|
There was a problem hiding this comment.
This section is largely based on the internal doc here, and needs thorough review:
https://oktawiki.atlassian.net/wiki/spaces/ISGI/pages/3431662076/RFC+CIBA+with+Email+and+SMS#Notification-Channel-Selection
should a flow diagram also be added?
priley86
commented
Oct 28, 2025
| - **User's enrolled authenticators**: if the user is not enrolled to use an MFA push authenticator, the current behavior is to fallback to Email instead of rejecting the request. | ||
| - **User's email verification status**: if the user's email is not verified, we assume sending emails to an unverified email address is not desired, and the request will be rejected. | ||
|
|
||
| You can read more about the notification channel selection in the [Configure Client-Initiated Backchannel Authentication](https://auth0.com/docs/get-started/applications/configure-client-initiated-backchannel-authentication) documentation. |
There was a problem hiding this comment.
are we planning to also enhance this page or any others related to CIBA within Auth0 docs for this @lrzhou25 ?
priley86
commented
Oct 28, 2025
| Asynchronous Authorization | ||
| </a> | ||
| {" "} documentation. | ||
| </Step>, |
There was a problem hiding this comment.
Preference here is to keep updates minimal within the quickstarts, and link back to an overview page about this overfall flow / notification logic. My thinking is this logic could evolve and seems this would be an ok place to make reference to the configuration and allow them to dive further should it be necessary.
priley86
changed the base branch from
main
to
feat/connected_accounts_doc_updates
priley86
force-pushed
the
async-auth-updates
branch
from
6340997 to
148636b
Compare
priley86
changed the base branch from
feat/connected_accounts_doc_updates
to
main
priley86
changed the base branch from
main
to
feat/connected_accounts_doc_updates
priley86
changed the base branch from
feat/connected_accounts_doc_updates
to
main
priley86
changed the base branch from
main
to
feat/connected_accounts_doc_updates
lrzhou25
force-pushed
the
feat/connected_accounts_doc_updates
branch
from
9381d2c to
770d1cb
Compare
pmalouin
approved these changes
Oct 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Adds some additional copy around CIBA Notification channels.
Some related PRs:
https://github.com/atko-cic/manhattan/pull/8138
https://github.com/atko-cic/auth0-server/pull/16424
References
JIRA: AIDX-130
Testing
Impacts the following pages:
Asynchronouis Authorization (overview page):
https://auth0-genai-async-auth-updates.mintlify.app/intro/asynchronous-authorization#user-consent-and-notification-channel-selection
Prerequisites (adds "Configure Notification Channel settings" section to all of the Async Authorization quickstarts):
https://auth0-genai-async-auth-updates.mintlify.app/get-started/asynchronous-authorization#prerequisites
Checklist