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

Implement data privacy provider #5

Closed
2 tasks
brendanheywood opened this issue Jan 25, 2023 · 1 comment · Fixed by #35
Closed
2 tasks

Implement data privacy provider #5

brendanheywood opened this issue Jan 25, 2023 · 1 comment · Fixed by #35
Assignees
Labels
enhancement New feature or request

Comments

@brendanheywood
Copy link
Contributor

brendanheywood commented Jan 25, 2023

This does record data from it doesn't send it anywhere, it is import only from the other site. So I think technically this doesn't store user data even though it does.

I think the best next option is to implement it in a way that allows an admin to login as to this person and make data requests on behalf of that person. Or if the psuedo users ever get turned into real accounts then it will magically just work.

Tasks:

  • implement a privacy provider that behaves correctly if somebody does a login as to the fake user
  • or same same - if the user is converted from a fake user into a real manual account
@brendanheywood brendanheywood added the enhancement New feature or request label Jan 25, 2023
@danmarsden
Copy link
Member

note this is a plugins db approval blocker when a plugin commiunicates with an external "thing/api" - which I think includes this plugin so it's probably also a blocker for approval.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants