Add OpenTelemetry support for passkey operations #2795
Draft
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
…cking and span management in PasskeyReplyChannel, PasskeyWebListener, and AzureActiveDirectoryWebViewClient
|
❌ Work item link check failed. Description does not contain AB#{ID}. Click here to Learn more. |
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.
This PR adds full OpenTelemetry tracing for passkey flows that use JS bridge and makes trace context consistent across the auth process.
What’s new:
PasskeyReplyChannel: Creates spans and sets attributes for success, errors, and send actions.
PasskeyWebListener: Accepts SpanContext, creates spans per message, and makes them current.
WebViewClient: Propagates parent SpanContext so all web view spans share the same trace.