Red Hat Bugzilla – Bug 1469470
Company Specific Messages table on the login page should gracefully handle large amounts of text.
Last modified: 2018-02-21 12:06:59 EST
Created attachment 1296175 [details] screenshot of UI Description of problem: The Company Specific Messages on the login page can cover all login page and the user interface under settings-> general tab breaks.Thus, there should be character limit. Version-Release number of selected component (if applicable): sat 6.3 snap 6.0 How reproducible: always Steps to Reproduce: 1. Navigate to Administer -> settings 2. Click on general tab 3. Enter large Login page footer message Actual results: Login page and UI under settings-> general breaks. Expected results: There should be constraint to character limit so that login page UI and settings-> general tab page should not break. Additional info:
I don't think there should be a limit. Instead, the settings should be able to resize the table accordingly to the content. In fact some of the requesters of the RFE https://bugzilla.redhat.com/show_bug.cgi?id=726570 ask for pretty large texts to be included.
Agree, to some degree, with comment #3. The proper way would be to assure table can gracefully handle a bunch of text. There probably should be some sort of validation, however, that someone can't DDoS or otherwise make a login screen unusable due to malicious (or inadvertent) inclusion of excessive content.
Created redmine issue http://projects.theforeman.org/issues/21200 from this bug
Upstream bug assigned to tstrachota@redhat.com
PR: https://github.com/theforeman/foreman/pull/4915
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21200 has been resolved.
VERIFIED Version Tested: Satellite-6.3 Snap 22 steps: 1. Inserted large text in Login page footer message parameter under settings Login page handled the larger data.
Created attachment 1345372 [details] Screenshot of login page
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:0336