Skip to content

option to customize sanitizeUserForClient function #46

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

Closed
markacola opened this issue May 30, 2017 · 1 comment · Fixed by #47
Closed

option to customize sanitizeUserForClient function #46

markacola opened this issue May 30, 2017 · 1 comment · Fixed by #47

Comments

@markacola
Copy link
Contributor

Steps to reproduce

I have a use case where sensitive data is stored on the user object, which has sanitation hooks on the user service when the provider is remote.
These sanitation hooks are circumvented by the authManagement service (it being a server-side call) leading to the entire user object being returned, and subsequently sent down to the client. In these cases the client may be completely anonymous.

Expected behavior

Should be able to customize the sanitation of the user returned from the authManagement service.

Actual behavior

User contains all data, save what the authManagement service deems appropriate to remove.

System configuration

N/A

I am happy to implement this an send a PR across, just let me know.

It might be beneficial to also allow customized functions for other helpers.

@eddyystop
Copy link
Collaborator

Being delt with in #47

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

Successfully merging a pull request may close this issue.

2 participants