-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Create a 'password' field type #1061
Comments
These are concerns that should be raised with the plugins themselves, as they are not secured correctly. Leaving this open as a reference to fix it. |
This comment has been minimized.
This comment has been minimized.
@LArbearrr this is an expected behaviour, the model's This is not a security concern as client's injecting fields in their own browser has no effect on what October sends the client in terms of model data and if you're talking about plugins extending the fields serverside, well it's much easier for them to just to |
Looking trough source code field type password already exists. |
A field widget that allows for entering of sensitive information that can be revealed at the user's request - ie. API keys, secrets. When a sensitive field that has been previously populated is loaded again, a placeholder is used instead of the real value, until the user opts to reveal the value. The real value is loaded via AJAX. Credit to @tomaszstrojny for the original implementation. Replaces #5062. Fixes #5061, #1850, perhaps #1061. Co-authored-by: Tomasz Strojny <[email protected]>
A field widget that allows for entering of sensitive information that can be revealed at the user's request - ie. API keys, secrets. When a sensitive field that has been previously populated is loaded again, a placeholder is used instead of the real value, until the user opts to reveal the value. The real value is loaded via AJAX. Credit to @tomaszstrojny for the original implementation. Replaces #5062. Fixes #5061, #1850, perhaps #1061. Co-authored-by: Tomasz Strojny <[email protected]> Co-authored-by: Luke Towers <[email protected]>
When you remove all permissions for a user, they still have access and can edit the MISC sub-category in settings on the backend which is terrible because some really important information that shouldn't be messed around with is there. To name a few plugins:
Google Analytics - Contains tons of keys & codes that will completely break it's dashboard functionality if changed.
Mailchimp - Contains the MailChimp API Key which would be very bad if changed by accident.
Disqus - Contains the Disqus API Site Key that would break comment section if changed.
The text was updated successfully, but these errors were encountered: