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

FedCM and GDPR regulations #533

Closed
dusekjan opened this issue Jan 4, 2024 · 2 comments
Closed

FedCM and GDPR regulations #533

dusekjan opened this issue Jan 4, 2024 · 2 comments

Comments

@dusekjan
Copy link

dusekjan commented Jan 4, 2024

Hello,
As identity providers, we must comply with the GDPR regulations within the European Union. We have already started experimenting with FedCM in development and I would like to ask if it will be possible to change or extend the list of user data (inside the disclosure text) that we as identity providers submit to the RP once the dialogue with FedCM has been agreed.

The problem is that we have to show the user in the FedCM dialog all his user data that we want to pass to the RP after clicking on "Continue as...".

Currently the disclosure text is as follows:

To continue, idp.com will share your name, email address, and profile picture with this site. See ...

In addition to the name, email, profile picture, we would need to append information about providing other data, for example whether the person is an adult or not. However, it would be best if we had full control over the user data displayed, ideally sending a list of all items in some HTTP response.

@npm1
Copy link
Collaborator

npm1 commented Jan 4, 2024

This seems related to #477. With that proposal, IDP can request custom scopes and the use a continue_on URL to display what they want to the user before providing the token to the RP. Does that seem like it would solve your use case?

@dusekjan
Copy link
Author

dusekjan commented Jan 5, 2024

Thanks for the reply.

Does that seem like it would solve your use case?

yes, it seems to me that this would solve the problem.

This seems related to #477.

I'll keep an eye on the news within this Issue, and when this new feature makes it into the documentation, I'll implement it.

@dusekjan dusekjan closed this as completed Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants