Skip to content
This repository has been archived by the owner on Jun 23, 2020. It is now read-only.

Don't send the value of password fields #16

Open
adamw opened this issue Dec 20, 2014 · 2 comments
Open

Don't send the value of password fields #16

adamw opened this issue Dec 20, 2014 · 2 comments

Comments

@adamw
Copy link
Member

adamw commented Dec 20, 2014

We need to detect that password fields have changed, an then store the new value, but we shouldn't send the raw value from the backing object.

Or maybe this should be handled by the user's code in handling the resulting backing object?

@szimano
Copy link
Member

szimano commented Dec 20, 2014

maybe this should be a general behaviour of a secret-rendered field? that the real value is neer sent to the frontend?

@adamw
Copy link
Member Author

adamw commented Dec 20, 2014

yes, that's what I meant :) but the field is currently called "password" in supler

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants