Skip to content

Add single-get multi IDP support for passive mode #686

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 15 commits into from
Mar 25, 2025
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
rebase
  • Loading branch information
npm1 committed Feb 19, 2025
commit 16c7ef2ee8644600b0ef5ca9084242047f6de381
6 changes: 3 additions & 3 deletions spec/index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -2580,11 +2580,11 @@ The [=remote end steps=] are:
1. Return [=success=] with data `null`.

<!-- ============================================================ -->
# Security Considerations # {#security-considerations}
# Security Considerations # {#security}
<!-- ============================================================ -->

This section provides a few of the security considerations for the FedCM API. Note that there is a
separate section for [[#privacy-considerations]].
separate section for [[#privacy]].

In FedCM, there are various assets that need to be protected. All of the endpoints need basic
protections, and the credentialed ones need protections from various kinds of attacks and threats.
Expand Down Expand Up @@ -2828,7 +2828,7 @@ the attacker's [=RP=] might also not be trusted by the [=IDP=], so the flow woul
{{id_assertion_endpoint_request/client_id}} or CORS checks.

<!-- ============================================================ -->
# Privacy Considerations # {#privacy-considerations}
# Privacy Considerations # {#privacy}
<!-- ============================================================ -->

This section is intended to provide a comprehensive overview of the privacy risks associated with
Expand Down