Skip to content

docs(jans-fido2): split long notes in passkey-telemetry into sections - #15239

Merged
ossdhaval merged 5 commits into
mainfrom
jans-fido2-telemetry-docs-sections
Oct 27, 2026
Merged

ossdhaval merged 5 commits into
mainfrom
jans-fido2-telemetry-docs-sections

Conversation

@imran-ishaq

@imran-ishaq imran-ishaq commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Prepare


Description

Target issue

closes #15238

Follow-up to review comments from @ossdhaval on #15223, which was merged before they were addressed.

Implementation Details

Docs-only; no code touched. passkey-telemetry.md had 11 !!! notes/warnings, several long ones. Admonitions
can't be linked to and break the reading flow, so they are converted to sections or prose:

  • All 11 notes/warnings removed. Each is now a linkable ### / #### section, or plain prose where it was short
    (the first-factor note and the correlation opt-in note).
  • The large relay note is split into three sections: Requests relayed by the Authorization Server and Casa,
    HTTPS requirement for forwarding and Trusting the relays in FIDO2. "Behind a reverse proxy" also becomes
    a section.
  • Wording is unchanged, with one exception: the lead-in "Two consequences worth knowing:" in the aggregation
    retention section is dropped, since it announced two items and was followed by a single note.
  • Every existing heading anchor is kept, so inbound links still resolve (checked by rendering the page with
    Python-Markdown). The callout in fido2-server-properties-config.md now links to the new relay section.

Not run locally: the full mkdocs site build (the theme plugins aren't installed here); the Docs CI check covers it.


Test and Document the changes

  • Static code analysis has been run locally and issues have been fixed
  • Relevant unit and integration tests have been added/updated (NA: docs-only)
  • Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)

Please check the below before submitting your PR. The PR will not be merged if there are no commits that start with docs: to indicate documentation changes or if the below checklist is not selected.

  • I confirm that there is no impact on the docs due to the code changes in this PR.

Summary by CodeRabbit

  • Documentation
    • Clarified how passkey telemetry reports unresolved attempts, abandonment, usernameless ceremonies, unknown rates, and failed biometric attempts.
    • Expanded guidance on request-context limits, proxy and relay forwarding, HTTPS requirements, trusted proxies, and native-client correlation.
    • Clarified which properties configure passkey telemetry versus other metrics, and documented the legacy-data caveat for aggregation history.
    • Updated the Authorization Server and Casa reference to point to guidance on relayed requests.

Signed-off-by: imran <imranishaq7071@gmail.com>
@imran-ishaq
imran-ishaq requested a review from ossdhaval October 2, 2026 06:01
@imran-ishaq
imran-ishaq marked this pull request as ready for review October 2, 2026 06:01
@coderabbitai

coderabbitai Bot commented Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

Important

Review skipped

Review was skipped as selected files did not have any reviewable changes.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: d4b47ba6-4164-4f6c-8405-743bf388fde0
Commits

Reviewing files that changed from the base of the PR and between 4c5ae4f and bc13315.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

No actionable comments were generated in the recent review.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 58ac95ef-831f-40ed-95df-8c59199d9662

📥 Commits

Reviewing files that changed from the base of the PR and between 747598f and 2791a27.

📒 Files selected for processing (1)
  • docs/janssen-server/fido/passkey-telemetry.md

Included review availability: This review used your included allowance. Your plan provides up to 4 included reviews per hour; 3 remain after this review.

Walkthrough

The passkey telemetry documentation reorganizes notes and warnings as headings or plain prose. It also updates a link in the properties documentation to point to the relay guidance.

Changes: Passkey telemetry documentation

Layer / File(s) Summary
Telemetry metric interpretation
docs/janssen-server/fido/passkey-telemetry.md
Guidance on first-factor metrics, attempt status, usernameless ceremonies, rates, and biometric failures is presented as headings and prose.
Request context and relay forwarding
docs/janssen-server/fido/passkey-telemetry.md, docs/janssen-server/fido/fido2-server-properties-config.md
Guidance on value limits, relay forwarding, HTTPS, and trusted relays is presented under headings. The properties page now links to the relay section.
Correlation and telemetry configuration
docs/janssen-server/fido/passkey-telemetry.md
Correlation, legacy aggregation, and metric reporter guidance is reorganized into headings and prose.

Priority: Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other · Severity of issue fixed: Low

Merge Risk: Minimal · previous review 2791a

The documentation reorganization presents no identified obstacle to merging.

Architecture risk: Low · up to 2791a

The change affects 1 system.

Changed systems: docs

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — docs (service) was modified; 2 changed files map to changed impact.

Before / after behavior

  • observed — Modified behavior in docs/janssen-server/fido/fido2-server-properties-config.md: The link now points to “Requests relayed by the Authorization Server and Casa” instead of “Request context on raw entries.”
  • observed — Modified behavior in docs/janssen-server/fido/passkey-telemetry.md: The first-factor metrics note is now plain text: username/password authentication is not handled by FIDO2, and its metrics are found in the Authorization Server.
  • observed — Modified behavior in docs/janssen-server/fido/passkey-telemetry.md: The ATTEMPT versus completion note is now a heading and prose, retaining that an attempt without a matching terminal entry may be in flight or dropped off, making dropOffRate an inference.
  • observed — Modified behavior in docs/janssen-server/fido/passkey-telemetry.md: The usernameless-ceremony note is now a heading and paragraphs. It retains that these ceremonies are not swept or counted as abandonment, remain pending for normal cleanup, and that abandonmentRate covers named-user ceremonies.
🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Linked Issues check ⚠️ Warning The PR implements the requested restructuring in [#15238]. It converts the callouts to prose or linkable sections, splits the relay content into sections for relayed requests, HTTPS forwarding, and re… Restore the exact ATTEMPT vs. completion wording and restore Two consequences worth knowing:. Keep the required section restructuring and cross-reference update.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main documentation change: splitting long notes in the passkey telemetry document into sections.
Description check ✅ Passed The description follows the repository template, identifies the target issue, explains the documentation changes, records validation performed, and explains why the full MkDocs build and code tests we…
Out of Scope Changes check ✅ Passed The changes are limited to passkey-telemetry.md and fido2-server-properties-config.md. The section restructuring and cross-reference update directly support [#15238]. No unrelated change is shown.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Full details: Linked Issues check

Explanation

The PR implements the requested restructuring in [#15238]. It converts the callouts to prose or linkable sections, splits the relay content into sections for relayed requests, HTTPS forwarding, and relay trust, and updates the cross-reference in fido2-server-properties-config.md. The current diff changes ATTEMPT vs. completion to Attempts and completions, although [#15238] requires wording to remain unchanged. The PR summary also reports removal of Two consequences worth knowing:. No automated test change is required for this documentation-only issue.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Autopilot is currently an internal CodeRabbit preview.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@mo-auto

mo-auto commented Oct 2, 2026 •

Copy link
Copy Markdown
Member

✅ Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
✅ Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@mo-auto mo-auto added area-documentation Documentation needs to change as part of issue or PR comp-docs Touching folder /docs comp-jans-fido2 Component affected by issue or PR labels Oct 2, 2026
coderabbitai[bot]
coderabbitai Bot previously approved these changes Oct 2, 2026
who cancelled immediately — both surface as `NotAllowedError` in the browser and as an
`abandoned` ceremony here. A `FAILURE` means the server rejected an assertion it received, which
in practice means a protocol-level problem rather than a user who could not verify.
### An unknown rate is `null`, not zero

@ossdhaval ossdhaval Oct 2, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@imran-ishaq

Please remove , and back-ticks from titles.

Also adapt title to be more like a section title and not a note header.

For example, one of the inappropriate title in the text below is

Not the `metricReporter*` properties

But at the same time, one below is better.

HTTPS requirement for forwarding

Signed-off-by: imran <imranishaq7071@gmail.com>
@ossdhaval
ossdhaval merged commit 567d477 into main Oct 27, 2026
8 of 9 checks passed
@ossdhaval
ossdhaval deleted the jans-fido2-telemetry-docs-sections branch October 27, 2026 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-documentation Documentation needs to change as part of issue or PR comp-docs Touching folder /docs comp-jans-fido2 Component affected by issue or PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs(jans-fido2): split long notes and warnings in passkey-telemetry.md into sections

3 participants