[JBoss JIRA] (RTGOV-332) Record message resubmission details against situation
by Michael Clay (JIRA)
[ https://issues.jboss.org/browse/RTGOV-332?page=com.atlassian.jira.plugin.... ]
Michael Clay resolved RTGOV-332.
--------------------------------
Resolution: Done
> Record message resubmission details against situation
> -----------------------------------------------------
>
> Key: RTGOV-332
> URL: https://issues.jboss.org/browse/RTGOV-332
> Project: RTGov (Run Time Governance)
> Issue Type: Feature Request
> Components: User Interface
> Reporter: Gary Brown
> Assignee: Michael Clay
>
> When message is resubmitted, record the date/time, who resubmitted it, and the status of the resubmission (success/fail) in the properties of the situation, and saved back to the db.
> If these properties exist on a situation - when the situation details are displayed, they should be displayed on the Message tab, so that user avoids resubmitting again if previously successful.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (SRAMP-384) Add validation for password in overlord commons installer
by Gary Brown (JIRA)
[ https://issues.jboss.org/browse/SRAMP-384?page=com.atlassian.jira.plugin.... ]
Gary Brown commented on SRAMP-384:
----------------------------------
For verification, can you also ask for the password to be re-entered, to confirm the values match - as this may lead to issues if the user inadvertently enters the wrong value.
> Add validation for password in overlord commons installer
> ---------------------------------------------------------
>
> Key: SRAMP-384
> URL: https://issues.jboss.org/browse/SRAMP-384
> Project: S-RAMP
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Eric Wittmann
> Assignee: Eric Wittmann
> Fix For: 0.4.1 - Bugfixes
>
>
> Currently the overlord commons installer is responsible for doing all security related work. This includes creating the overlord 'admin' user and configured a password for this user. The installer prompts the user for this password and then passes whatever the user entered to the JBoss EAP add-user utility. This utility will fail if the password does not meet certain standards. However, the utility fails without failing the overall install.
> The installer should do its own validation of the password entered by the user so that this silent failure doesn't happen. Also note that the password input and validation should happen before anything else security related gets installed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (SRAMP-384) Add validation for password in overlord commons installer
by Eric Wittmann (JIRA)
Eric Wittmann created SRAMP-384:
-----------------------------------
Summary: Add validation for password in overlord commons installer
Key: SRAMP-384
URL: https://issues.jboss.org/browse/SRAMP-384
Project: S-RAMP
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: Eric Wittmann
Assignee: Eric Wittmann
Fix For: 0.4.1 - Bugfixes
Currently the overlord commons installer is responsible for doing all security related work. This includes creating the overlord 'admin' user and configured a password for this user. The installer prompts the user for this password and then passes whatever the user entered to the JBoss EAP add-user utility. This utility will fail if the password does not meet certain standards. However, the utility fails without failing the overall install.
The installer should do its own validation of the password entered by the user so that this silent failure doesn't happen. Also note that the password input and validation should happen before anything else security related gets installed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months