Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 3.0.0.b4
-
Fix Version/s: 4.3.0-b1
-
Component/s: Client Interface, Staff Interface
-
Labels:None
Description
To setup password-autogeneration, add a set of data attributes to a clickable element, which will open a modal and allow you to generate a password.
The clickable element must have the class name generate-password to automatically be set as a password-generating modal.
The following data attributes must be set on the generate-password-class element:
- data-base-url The base URL of the Blesta installation. This is generally the value of $this->base_uri in php
- data-for-class The name of a CSS class to set the generated password to. HTML elements of this class will be set the password
- data-length The length of the password to generate (e.g. 10)
- data-options A string-representation of JSON data representing characters to include in the password generator. This must be formatted as described in unicode-passgen.
- The below example will include all latin alpha characters lower-case and upper-case from A to Z, but exclude the lower and upper-case letter 'i'.
- {"include": [{"chars": [["A", "Z"], ["a", "z"]]}], "exclude": [{"chars": [["i"], ["I"]]}]}
The following data attributes are optional:
- data-modal-title This is the title to set for the modal. By default, it will use the text of the generate-password element
- (Admin UI only) data-modal-close This is the name to set as the close button language, e.g. 'Close'
Password fields are used throughout the system, (in core, modules, etc.) many of which need 2 fields (one for the password, one for confirmation).
We would like to include a simple Blesta core-javascript function for generating a modal, allowing a password to be generated and auto-populate the password fields. It will show the user the plaintext password so they can copy it (like cPanel).
A simple "data-generate-password='unique_field'" attribute to the input field(s) would auto-set this modal to the form next to the field. I imagine the attribute should contain a unique value per SET of fields to which the password should apply.
e.g.
if we have password and confirm_password fields, they should both have the same attribute value so that we only display the "generate password" link next to the first field, instead of both, and both will still be updated when a password is generated.
Issue Links
Activity
Field | Original Value | New Value |
---|---|---|
Fix Version/s | 3.3.0 [ 10100 ] | |
Fix Version/s | 3.1.0 [ 10001 ] |
Security | Private [ 10000 ] |
Fix Version/s | 3.3.0-b2 [ 10507 ] | |
Fix Version/s | 3.3.0-b1 [ 10100 ] |
Fix Version/s | 3.3.0 [ 10508 ] | |
Fix Version/s | 3.3.0-b2 [ 10507 ] |
Fix Version/s | 3.4.0 [ 10400 ] | |
Fix Version/s | 3.3.0 [ 10508 ] |
Fix Version/s | 3.4.0 [ 10400 ] |
Fix Version/s | Long Term [ 10801 ] |
Attachment | passwd-selector.png [ 11651 ] |
Rank | Ranked higher |
Story Points | 8 |
Fix Version/s | 4.3.0 [ 11022 ] | |
Fix Version/s | Long Term [ 10801 ] |
Sprint | 4.3.0 Sprint 5 [ 55 ] |
Sprint | 4.3.0 Sprint 5 [ 55 ] | 4.3.0 Sprint 4 [ 54 ] |
Rank | Ranked higher |
Remaining Estimate | 0 minutes [ 0 ] | |
Time Spent | 29 minutes [ 1740 ] | |
Worklog Id | 10784 [ 10784 ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Time Spent | 29 minutes [ 1740 ] | 4 hours, 1 minute [ 14460 ] |
Worklog Id | 10791 [ 10791 ] |
Time Spent | 4 hours, 1 minute [ 14460 ] | 4 hours, 54 minutes [ 17640 ] |
Worklog Id | 10792 [ 10792 ] |
Time Spent | 4 hours, 54 minutes [ 17640 ] | 1 day, 42 minutes [ 31320 ] |
Worklog Id | 10795 [ 10795 ] |
Time Spent | 1 day, 42 minutes [ 31320 ] | 1 day, 3 hours, 38 minutes [ 41880 ] |
Worklog Id | 10809 [ 10809 ] |
Time Spent | 1 day, 3 hours, 38 minutes [ 41880 ] | 2 days, 7 minutes [ 58020 ] |
Worklog Id | 10816 [ 10816 ] |
Time Spent | 2 days, 7 minutes [ 58020 ] | 2 days, 1 hour, 14 minutes [ 62040 ] |
Worklog Id | 10822 [ 10822 ] |
Time Spent | 2 days, 1 hour, 14 minutes [ 62040 ] | 2 days, 2 hours, 44 minutes [ 67440 ] |
Worklog Id | 10823 [ 10823 ] |
Description |
Password fields are used throughout the system, (in core, modules, etc.) many of which need 2 fields (one for the password, one for confirmation).
We would like to include a simple Blesta core-javascript function for generating a modal, allowing a password to be generated and auto-populate the password fields. It will show the user the plaintext password so they can copy it (like cPanel). A simple "data-generate-password='unique_field'" attribute to the input field(s) would auto-set this modal to the form next to the field. I imagine the attribute should contain a unique value per SET of fields to which the password should apply. e.g. if we have password and confirm_password fields, they should both have the same attribute value so that we only display the "generate password" link next to the first field, instead of both, and both will still be updated when a password is generated. |
To setup password-autogeneration, add a set of data attributes to a clickable element, which will open a modal and allow you to generate a password.
The clickable element must have the class name *generate-password* to automatically be set as a password-generating modal. The following data attributes *must* be set on the *generate-password*-class element: * data-base-url The base URL of the Blesta installation. This is generally the value of _$this->base_uri_ in php * data-for-class The name of a CSS class to set the generated password to. HTML elements of this class will be set the password * data-length The length of the password to generate (e.g. 10) * data-options A string-representation of JSON data representing characters to include in the password generator. This must be formatted as described in [unicode-passgen|https://github.com/phillipsdata/unicode-passgen#api]. ** The below example will include all latin alpha characters lower-case and upper-case from A to Z, but exclude the lower and upper-case letter 'i'. ** \{"include": \[\{"chars": \[\["A", "Z"\], \["a", "z"\]\]\}\], "exclude": \[\{"chars": \[\["i"\], \["I"\]\]\}\]\} The following data attributes are optional: - data-modal-title This is the title to set for the modal. By default, it will use the text of the *generate-password* element - data-modal-close This is the name to set as the close button language, e.g. 'Close' ---- Password fields are used throughout the system, (in core, modules, etc.) many of which need 2 fields (one for the password, one for confirmation). We would like to include a simple Blesta core-javascript function for generating a modal, allowing a password to be generated and auto-populate the password fields. It will show the user the plaintext password so they can copy it (like cPanel). A simple "data-generate-password='unique_field'" attribute to the input field(s) would auto-set this modal to the form next to the field. I imagine the attribute should contain a unique value per SET of fields to which the password should apply. e.g. if we have password and confirm_password fields, they should both have the same attribute value so that we only display the "generate password" link next to the first field, instead of both, and both will still be updated when a password is generated. |
Description |
To setup password-autogeneration, add a set of data attributes to a clickable element, which will open a modal and allow you to generate a password.
The clickable element must have the class name *generate-password* to automatically be set as a password-generating modal. The following data attributes *must* be set on the *generate-password*-class element: * data-base-url The base URL of the Blesta installation. This is generally the value of _$this->base_uri_ in php * data-for-class The name of a CSS class to set the generated password to. HTML elements of this class will be set the password * data-length The length of the password to generate (e.g. 10) * data-options A string-representation of JSON data representing characters to include in the password generator. This must be formatted as described in [unicode-passgen|https://github.com/phillipsdata/unicode-passgen#api]. ** The below example will include all latin alpha characters lower-case and upper-case from A to Z, but exclude the lower and upper-case letter 'i'. ** \{"include": \[\{"chars": \[\["A", "Z"\], \["a", "z"\]\]\}\], "exclude": \[\{"chars": \[\["i"\], \["I"\]\]\}\]\} The following data attributes are optional: - data-modal-title This is the title to set for the modal. By default, it will use the text of the *generate-password* element - data-modal-close This is the name to set as the close button language, e.g. 'Close' ---- Password fields are used throughout the system, (in core, modules, etc.) many of which need 2 fields (one for the password, one for confirmation). We would like to include a simple Blesta core-javascript function for generating a modal, allowing a password to be generated and auto-populate the password fields. It will show the user the plaintext password so they can copy it (like cPanel). A simple "data-generate-password='unique_field'" attribute to the input field(s) would auto-set this modal to the form next to the field. I imagine the attribute should contain a unique value per SET of fields to which the password should apply. e.g. if we have password and confirm_password fields, they should both have the same attribute value so that we only display the "generate password" link next to the first field, instead of both, and both will still be updated when a password is generated. |
To setup password-autogeneration, add a set of data attributes to a clickable element, which will open a modal and allow you to generate a password.
The clickable element must have the class name *generate-password* to automatically be set as a password-generating modal. The following data attributes *must* be set on the *generate-password*-class element: * _data-base-url_ The base URL of the Blesta installation. This is generally the value of _$this->base_uri_ in php * _data-for-class_ The name of a CSS class to set the generated password to. HTML elements of this class will be set the password * _data-length_ The length of the password to generate (e.g. 10) * _data-options_ A string-representation of JSON data representing characters to include in the password generator. This must be formatted as described in [unicode-passgen|https://github.com/phillipsdata/unicode-passgen#api]. ** The below example will include all latin alpha characters lower-case and upper-case from A to Z, but exclude the lower and upper-case letter 'i'. ** \{"include": \[\{"chars": \[\["A", "Z"\], \["a", "z"\]\]\}\], "exclude": \[\{"chars": \[\["i"\], \["I"\]\]\}\]\} The following data attributes are optional: - _data-modal-title_ This is the title to set for the modal. By default, it will use the text of the *generate-password* element - _data-modal-close_ This is the name to set as the close button language, e.g. 'Close' ---- Password fields are used throughout the system, (in core, modules, etc.) many of which need 2 fields (one for the password, one for confirmation). We would like to include a simple Blesta core-javascript function for generating a modal, allowing a password to be generated and auto-populate the password fields. It will show the user the plaintext password so they can copy it (like cPanel). A simple "data-generate-password='unique_field'" attribute to the input field(s) would auto-set this modal to the form next to the field. I imagine the attribute should contain a unique value per SET of fields to which the password should apply. e.g. if we have password and confirm_password fields, they should both have the same attribute value so that we only display the "generate password" link next to the first field, instead of both, and both will still be updated when a password is generated. |
Description |
To setup password-autogeneration, add a set of data attributes to a clickable element, which will open a modal and allow you to generate a password.
The clickable element must have the class name *generate-password* to automatically be set as a password-generating modal. The following data attributes *must* be set on the *generate-password*-class element: * _data-base-url_ The base URL of the Blesta installation. This is generally the value of _$this->base_uri_ in php * _data-for-class_ The name of a CSS class to set the generated password to. HTML elements of this class will be set the password * _data-length_ The length of the password to generate (e.g. 10) * _data-options_ A string-representation of JSON data representing characters to include in the password generator. This must be formatted as described in [unicode-passgen|https://github.com/phillipsdata/unicode-passgen#api]. ** The below example will include all latin alpha characters lower-case and upper-case from A to Z, but exclude the lower and upper-case letter 'i'. ** \{"include": \[\{"chars": \[\["A", "Z"\], \["a", "z"\]\]\}\], "exclude": \[\{"chars": \[\["i"\], \["I"\]\]\}\]\} The following data attributes are optional: - _data-modal-title_ This is the title to set for the modal. By default, it will use the text of the *generate-password* element - _data-modal-close_ This is the name to set as the close button language, e.g. 'Close' ---- Password fields are used throughout the system, (in core, modules, etc.) many of which need 2 fields (one for the password, one for confirmation). We would like to include a simple Blesta core-javascript function for generating a modal, allowing a password to be generated and auto-populate the password fields. It will show the user the plaintext password so they can copy it (like cPanel). A simple "data-generate-password='unique_field'" attribute to the input field(s) would auto-set this modal to the form next to the field. I imagine the attribute should contain a unique value per SET of fields to which the password should apply. e.g. if we have password and confirm_password fields, they should both have the same attribute value so that we only display the "generate password" link next to the first field, instead of both, and both will still be updated when a password is generated. |
To setup password-autogeneration, add a set of data attributes to a clickable element, which will open a modal and allow you to generate a password.
The clickable element must have the class name *generate-password* to automatically be set as a password-generating modal. The following data attributes *must* be set on the *generate-password*-class element: * _data-base-url_ The base URL of the Blesta installation. This is generally the value of _$this->base_uri_ in php * _data-for-class_ The name of a CSS class to set the generated password to. HTML elements of this class will be set the password * _data-length_ The length of the password to generate (e.g. 10) * _data-options_ A string-representation of JSON data representing characters to include in the password generator. This must be formatted as described in [unicode-passgen|https://github.com/phillipsdata/unicode-passgen#syntax-for-options]. ** The below example will include all latin alpha characters lower-case and upper-case from A to Z, but exclude the lower and upper-case letter 'i'. ** \{"include": \[\{"chars": \[\["A", "Z"\], \["a", "z"\]\]\}\], "exclude": \[\{"chars": \[\["i"\], \["I"\]\]\}\]\} The following data attributes are optional: - _data-modal-title_ This is the title to set for the modal. By default, it will use the text of the *generate-password* element - _data-modal-close_ This is the name to set as the close button language, e.g. 'Close' ---- Password fields are used throughout the system, (in core, modules, etc.) many of which need 2 fields (one for the password, one for confirmation). We would like to include a simple Blesta core-javascript function for generating a modal, allowing a password to be generated and auto-populate the password fields. It will show the user the plaintext password so they can copy it (like cPanel). A simple "data-generate-password='unique_field'" attribute to the input field(s) would auto-set this modal to the form next to the field. I imagine the attribute should contain a unique value per SET of fields to which the password should apply. e.g. if we have password and confirm_password fields, they should both have the same attribute value so that we only display the "generate password" link next to the first field, instead of both, and both will still be updated when a password is generated. |
Time Spent | 2 days, 2 hours, 44 minutes [ 67440 ] | 2 days, 6 hours, 19 minutes [ 80340 ] |
Worklog Id | 10824 [ 10824 ] |
Sprint | 4.3.0 Sprint 4 [ 54 ] | 4.3.0 Sprint 4, 4.3.0 Sprint 5 [ 54, 55 ] |
Rank | Ranked higher |
Time Spent | 2 days, 6 hours, 19 minutes [ 80340 ] | 3 days, 19 minutes [ 87540 ] |
Worklog Id | 10827 [ 10827 ] |
Time Spent | 3 days, 19 minutes [ 87540 ] | 3 days, 38 minutes [ 88680 ] |
Worklog Id | 10828 [ 10828 ] |
Time Spent | 3 days, 38 minutes [ 88680 ] | 3 days, 1 hour, 26 minutes [ 91560 ] |
Worklog Id | 10829 [ 10829 ] |
Description |
To setup password-autogeneration, add a set of data attributes to a clickable element, which will open a modal and allow you to generate a password.
The clickable element must have the class name *generate-password* to automatically be set as a password-generating modal. The following data attributes *must* be set on the *generate-password*-class element: * _data-base-url_ The base URL of the Blesta installation. This is generally the value of _$this->base_uri_ in php * _data-for-class_ The name of a CSS class to set the generated password to. HTML elements of this class will be set the password * _data-length_ The length of the password to generate (e.g. 10) * _data-options_ A string-representation of JSON data representing characters to include in the password generator. This must be formatted as described in [unicode-passgen|https://github.com/phillipsdata/unicode-passgen#syntax-for-options]. ** The below example will include all latin alpha characters lower-case and upper-case from A to Z, but exclude the lower and upper-case letter 'i'. ** \{"include": \[\{"chars": \[\["A", "Z"\], \["a", "z"\]\]\}\], "exclude": \[\{"chars": \[\["i"\], \["I"\]\]\}\]\} The following data attributes are optional: - _data-modal-title_ This is the title to set for the modal. By default, it will use the text of the *generate-password* element - _data-modal-close_ This is the name to set as the close button language, e.g. 'Close' ---- Password fields are used throughout the system, (in core, modules, etc.) many of which need 2 fields (one for the password, one for confirmation). We would like to include a simple Blesta core-javascript function for generating a modal, allowing a password to be generated and auto-populate the password fields. It will show the user the plaintext password so they can copy it (like cPanel). A simple "data-generate-password='unique_field'" attribute to the input field(s) would auto-set this modal to the form next to the field. I imagine the attribute should contain a unique value per SET of fields to which the password should apply. e.g. if we have password and confirm_password fields, they should both have the same attribute value so that we only display the "generate password" link next to the first field, instead of both, and both will still be updated when a password is generated. |
To setup password-autogeneration, add a set of data attributes to a clickable element, which will open a modal and allow you to generate a password.
The clickable element must have the class name *generate-password* to automatically be set as a password-generating modal. The following data attributes *must* be set on the *generate-password*-class element: * _data-base-url_ The base URL of the Blesta installation. This is generally the value of _$this->base_uri_ in php * _data-for-class_ The name of a CSS class to set the generated password to. HTML elements of this class will be set the password * _data-length_ The length of the password to generate (e.g. 10) * _data-options_ A string-representation of JSON data representing characters to include in the password generator. This must be formatted as described in [unicode-passgen|https://github.com/phillipsdata/unicode-passgen#syntax-for-options]. ** The below example will include all latin alpha characters lower-case and upper-case from A to Z, but exclude the lower and upper-case letter 'i'. ** \{"include": \[\{"chars": \[\["A", "Z"\], \["a", "z"\]\]\}\], "exclude": \[\{"chars": \[\["i"\], \["I"\]\]\}\]\} The following data attributes are optional: - _data-modal-title_ This is the title to set for the modal. By default, it will use the text of the *generate-password* element - (*Admin UI only*) _data-modal-close_ This is the name to set as the close button language, e.g. 'Close' ---- Password fields are used throughout the system, (in core, modules, etc.) many of which need 2 fields (one for the password, one for confirmation). We would like to include a simple Blesta core-javascript function for generating a modal, allowing a password to be generated and auto-populate the password fields. It will show the user the plaintext password so they can copy it (like cPanel). A simple "data-generate-password='unique_field'" attribute to the input field(s) would auto-set this modal to the form next to the field. I imagine the attribute should contain a unique value per SET of fields to which the password should apply. e.g. if we have password and confirm_password fields, they should both have the same attribute value so that we only display the "generate password" link next to the first field, instead of both, and both will still be updated when a password is generated. |
Status | In Progress [ 3 ] | In Review [ 5 ] |
Resolution | Fixed [ 1 ] |
Time Spent | 3 days, 1 hour, 26 minutes [ 91560 ] | 3 days, 3 hours, 27 minutes [ 98820 ] |
Worklog Id | 10831 [ 10831 ] |
Time Spent | 3 days, 3 hours, 27 minutes [ 98820 ] | 3 days, 4 hours, 12 minutes [ 101520 ] |
Worklog Id | 10900 [ 10900 ] |
Sprint | 4.3.0 Sprint 4, 4.3.0 Sprint 5 [ 54, 55 ] | 4.3.0 Sprint 4, 4.3.0 Sprint 5, 4.3.0 Sprint 6 [ 54, 55, 56 ] |
Status | In Review [ 5 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] | |
Status | Closed [ 6 ] | Reopened [ 4 ] |
Fix Version/s | 4.3.0-b1 [ 11019 ] | |
Fix Version/s | 4.3.0 [ 11022 ] |
Status | Reopened [ 4 ] | Closed [ 6 ] |
Resolution | Fixed [ 1 ] |