[MGNLPUR-142] Password inputs should not be escaped or encoded Created: 15/Sep/14  Updated: 20/Sep/19  Resolved: 20/Sep/19

Status: Closed
Project: Magnolia Public User Registration
Component/s: None
Affects Version/s: 2.4
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
dependency
depends upon MGNLFORM-236 Html escaping of form fields should b... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Epic Link: Support
Story Points: 3

 Description   

Password fields (and all fields generated by Form Module) encode HTML entities, but they should not - because for example '&' should be usable in a password.
It is additionally confusing because editing/inputting passwords within adminCentral - for example in the security app does not encode the inputs.

IN PUR module - all password fields must not change user input. Possibly this would be configured via the linked FORM ticket. But perhaps this will be implemented in another way.



 Comments   
Comment by Simon Lutz [ 20/Sep/19 ]

Duplicate of MGNLFORM-279

Generated at Mon Feb 12 06:43:29 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.