Skip to content
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

Add a worth-prototyping position for FedCM #676

Merged
merged 2 commits into from
Aug 31, 2022

Conversation

martinthomson
Copy link
Member

There is a lot to unpack here. We can't say that this is an unqualified
good, particularly given the effect that it might have on IdPs and RPs.
But we can at least signal some amount of positive interest.

cc @bvandersloot-mozilla

Closes #618.

There is a lot to unpack here.  We can't say that this is an unqualified
good, particularly given the effect that it might have on IdPs and RPs.
But we can at least signal some amount of positive interest.

Closes mozilla#618.
activities.json Outdated Show resolved Hide resolved
Copy link
Contributor

@bvandersloot-mozilla bvandersloot-mozilla left a comment

Choose a reason for hiding this comment

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

LGTM

"mdnUrl": null,
"mozBugUrl": "https://bugzilla.mozilla.org/show_bug.cgi?id=1782066",
"mozPosition": "positive",
"mozPositionDetail": "Federated login is a widely-used feature on the web with significant user benefits in usability and security. Unfortunately, federated identity on the web relies on the same techniques that are used to track web users. The Federated Credential Management API puts the browser in control of managing cross-site logins. Browsers can use this API as a way to give web users better ability to control and monitor how their identity - and any information related to their identity - is exchanged between sites. Including the browser in a mediating role will adversely affect some cross-site interactions, in some cases making them less efficient or even less usable. However, Mozilla considers it imperative that this change occur so that users can be granted control - and awareness - of all instances where their information is transferred between sites. This proposal provides browsers with the opportunity to provide these capabilities. Note that Mozilla also wants to acknowledge an important privacy compromise in the proposal: identity providers learn when and where the identity they provide is used. Though alternative designs might be technically possible, this approach recognizes the security benefits gained by allowing identity providers the ability to audit logins. Furthermore, though this design enables an authorized identity to track cross-site activity, it only does so with the direct permission and knowledge of users.",
Copy link
Contributor

Choose a reason for hiding this comment

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

This looks good. It captures the core conflicts in the space and how they are resolved by this proposal at a high level.

Copy link
Member

@tantek tantek left a comment

Choose a reason for hiding this comment

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

LGTM and accurately summarizes concerns noted in issue #618.

@martinthomson
Copy link
Member Author

Thanks Tantek. Moving on.

@martinthomson martinthomson merged commit 871e866 into mozilla:main Aug 31, 2022
@martinthomson martinthomson deleted the fedcm branch August 31, 2022 01:52
Daasin pushed a commit to Daasin/standards-positions that referenced this pull request Jan 5, 2023
* Add a worth-prototyping position for FedCM

There is a lot to unpack here.  We can't say that this is an unqualified
good, particularly given the effect that it might have on IdPs and RPs.
But we can at least signal some amount of positive interest.

Closes mozilla#618.

* new taxonomy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants