Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-2584

SolusVM: Generate a password automatically for client root password changes

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.2.0
    • Fix Version/s: 4.3.0-b1
    • Component/s: Modules
    • Labels:
      None

      Description

      When managing a SolusVM service (admin or client), there is a tab to change the root password.

      1. Update the root password box to add a link/button to Generate Password
        • This Generate Password button will open a modal to allow a password to be generated, as described in CORE-552
        • The password should be alphanumeric, i.e. lower-case and upper-case A-Z characters, and 0-9 characters
        • The password length appears to support anywhere from 6 to 50 characters, but we'll go with a 25 character length
        • After generating the password using the modal, it should update both the Password field and Confirm Password field and be saved accordingly upon submission

      When managing a SolusVM service, clients can reset the root password. Clients may choose a password that is rejected by SolusVM's API, or one that is very weak.

      Change this option so that Blesta generates a new password automatically.

      Currently clients click the "Change Password" button, then enter the new password twice and click "Change Password" button below that form. Instead of the "New Root Password" and "Confirm Root Password" fields, generate a new password here and display it instead.

      New Root Password
      PASSW0RD-GENERATED-HERE (Large text, possibly in a well)

      Replace the second "Change Password" button with a check box that says:

      [x] I have saved the above password
      [ SAVE BUTTON ]

      The checkbox must be checked before the password can be updated.

      This will solve both of these problems. We can generate a secure password, one that will not be rejected by SolusVM's API.

      I don't think anything needs to change on the admin side, we may wish admins to be able to set a specific password.

        Issue Links

          Activity

          Automated transition triggered when Tyson Phillips (Inactive) merged pull request #11 in Stash -
          Status In Review [ 5 ] Closed [ 6 ]
          jonathan Jonathan Reissmueller made changes -
          Time Spent 1 hour, 20 minutes [ 4800 ] 1 hour, 25 minutes [ 5100 ]
          Worklog Id 10991 [ 10991 ]
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked higher
          tyson Tyson Phillips (Inactive) made changes -
          Sprint 4.3.0 Sprint 6, 4.3.0 Sprint 7 [ 56, 57 ] 4.3.0 Sprint 6, 4.3.0 Sprint 7, 4.3.0 Sprint 8 [ 56, 57, 58 ]
          jonathan Jonathan Reissmueller made changes -
          Time Spent 1 hour, 15 minutes [ 4500 ] 1 hour, 20 minutes [ 4800 ]
          Worklog Id 10972 [ 10972 ]
          jonathan Jonathan Reissmueller made changes -
          Time Spent 1 hour, 10 minutes [ 4200 ] 1 hour, 15 minutes [ 4500 ]
          Worklog Id 10972 [ 10972 ]
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked higher
          tyson Tyson Phillips (Inactive) made changes -
          Sprint 4.3.0 Sprint 6 [ 56 ] 4.3.0 Sprint 6, 4.3.0 Sprint 7 [ 56, 57 ]
          jonathan Jonathan Reissmueller made changes -
          Remaining Estimate 30 minutes [ 1800 ] 0 minutes [ 0 ]
          Time Spent 22 minutes [ 1320 ] 1 hour, 10 minutes [ 4200 ]
          Worklog Id 10948 [ 10948 ]
          jonathan Jonathan Reissmueller made changes -
          Remaining Estimate 0 minutes [ 0 ] 30 minutes [ 1800 ]
          Time Spent 52 minutes [ 3120 ] 22 minutes [ 1320 ]
          Worklog Id 10928 [ 10928 ]
          Worklog Time Spent 30 minutes [ 1800 ]
          jonathan Jonathan Reissmueller made changes -
          Time Spent 22 minutes [ 1320 ] 52 minutes [ 3120 ]
          Worklog Id 10928 [ 10928 ]
          jonathan Jonathan Reissmueller made changes -
          Remaining Estimate 0 minutes [ 0 ]
          Time Spent 22 minutes [ 1320 ]
          Worklog Id 10927 [ 10927 ]
          Automated transition triggered when Jonathan Reissmueller created pull request #11 in Stash -
          Status In Progress [ 3 ] In Review [ 5 ]
          Resolution Fixed [ 1 ]
          Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
          Status Open [ 1 ] In Progress [ 3 ]
          jonathan Jonathan Reissmueller made changes -
          Assignee Jonathan Reissmueller [ jonathan ]
          tyson Tyson Phillips (Inactive) made changes -
          Fix Version/s 4.3.0-b1 [ 11019 ]
          Fix Version/s 4.3.0 [ 11022 ]
          tyson Tyson Phillips (Inactive) made changes -
          Description When managing a SolusVM service, clients can reset the root password. Clients may choose a password that is rejected by SolusVM's API, or one that is very weak.

          Change this option so that Blesta generates a new password automatically.

          Currently clients click the "Change Password" button, then enter the new password twice and click "Change Password" button below that form. Instead of the "New Root Password" and "Confirm Root Password" fields, generate a new password here and display it instead.

          *New Root Password*
          PASSW0RD-GENERATED-HERE (Large text, possibly in a well)

          Replace the second "Change Password" button with a check box that says:

          [x] I have saved the above password
          [ SAVE BUTTON ]

          The checkbox must be checked before the password can be updated.

          This will solve both of these problems. We can generate a secure password, one that will not be rejected by SolusVM's API.

          I don't think anything needs to change on the admin side, we may wish admins to be able to set a specific password.
          When managing a SolusVM service (admin or client), there is a tab to change the root password.
          # Update the root password box to add a link/button to _Generate Password_
          #* This _Generate Password_ button will open a modal to allow a password to be generated, as described in CORE-552
          #* The password should be alphanumeric, i.e. lower-case and upper-case A-Z characters, and 0-9 characters
          #* The password length appears to support anywhere from 6 to 50 characters, but we'll go with a 25 character length
          #* After generating the password using the modal, it should update both the _Password_ field and _Confirm Password_ field and be saved accordingly upon submission

          ----

          When managing a SolusVM service, clients can reset the root password. Clients may choose a password that is rejected by SolusVM's API, or one that is very weak.

          Change this option so that Blesta generates a new password automatically.

          Currently clients click the "Change Password" button, then enter the new password twice and click "Change Password" button below that form. Instead of the "New Root Password" and "Confirm Root Password" fields, generate a new password here and display it instead.

          *New Root Password*
          PASSW0RD-GENERATED-HERE (Large text, possibly in a well)

          Replace the second "Change Password" button with a check box that says:

          [x] I have saved the above password
          [ SAVE BUTTON ]

          The checkbox must be checked before the password can be updated.

          This will solve both of these problems. We can generate a secure password, one that will not be rejected by SolusVM's API.

          I don't think anything needs to change on the admin side, we may wish admins to be able to set a specific password.
          tyson Tyson Phillips (Inactive) made changes -
          Sprint 4.3.0 Sprint 6 [ 56 ]
          tyson Tyson Phillips (Inactive) made changes -
          Story Points 2
          tyson Tyson Phillips (Inactive) made changes -
          Link This issue is blocked by CORE-552 [ CORE-552 ]
          tyson Tyson Phillips (Inactive) made changes -
          Field Original Value New Value
          Rank Ranked higher
          admin Paul Phillips created issue -

            People

            • Assignee:
              jonathan Jonathan Reissmueller
              Reporter:
              admin Paul Phillips
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                15/Jun/18

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 1 hour, 25 minutes
                1h 25m

                  Agile