Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 4.6.0
-
Component/s: Plugins, Staff Interface
-
Labels:None
Description
It may be necessary to have new customers verify their email address prior to accepting an order or allowing certain functionality through extensions. Blesta core should be aware of and handle email verification, and the order plugin should be able to enforce it.
New Setting
Add a new setting for the company and client group to require email verification for new accounts. This would apply to both the client (primary contact) and any other contacts.
When a contact or client is created in the client group or company, based on the setting, send an email to the contact with a special link that can be used to validate their email address. Track whether an email address has been verified. The link should not have an expiry like password resets.
UI
If the setting is enabled and the email address has not been verified, display a warning in the client area with an option to resend the verification email. We may want to stop showing the message after a period of time if the user does not verify their email.
Functionality
Email address changes should not take affect until the address is verified. We will need to store the new email address and only update the official record when the verification link is clicked. This is necessary for security reasons, through 3rd party plugins that may trust the email address and associate it with an external account, like Kayako.
A method to check whether an email address has been verified should be available over the API, so such a method should not be private. Plugins may want to check whether an address has been verified, and thus can be trusted.
See sub-tasks for full/updated details.
Issue Links
- relates to
-
CORE-2222
Add additional client status of "Closed" and "In Review"
-
- Open
-
1. |
Add verification email template |  |
Closed | Abdy Franco |
|
||||||||
2. |
Add email verification setting | |
Closed | Abdy Franco |
|
||||||||
3. |
Add email_verifications table and model | |
Closed | Abdy Franco |
|
||||||||
4. |
Implement email verifications | |
Closed | Abdy Franco |
|
||||||||
5. |
Order: Send email verification on signup | |
Closed | Abdy Franco |
|
Activity
Paul Phillips
created issue -
| Rank | Ranked higher |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Fix Version/s | 4.12.0-b1 [ 11502 ] |
| Sprint | 4.12.0 Sprint 1 [ 112 ] |
| Rank | Ranked lower |
| Sprint | 4.12.0 Sprint 1 [ 112 ] |
| Rank | Ranked higher |
| Story Points | 8 |
| Sprint | 4.12.0 Sprint 1 [ 112 ] |
| Rank | Ranked lower |
| Description |
It may be necessary to have new customers verify their email address prior to accepting an order or allowing certain functionality through extensions. Blesta core should be aware of and handle email verification, and the order plugin should be able to enforce it.
h2. New Setting Add a new setting for the company and client group to require email verification for new accounts. This would apply to both the client (primary contact) and any other contacts. h2. Email When a contact or client is created in the client group or company, based on the setting, send an email to the contact with a special link that can be used to validate their email address. Track whether an email address has been verified. The link should not have an expiry like password resets. h2. UI If the setting is enabled and the email address has not been verified, display a warning in the client area with an option to resend the verification email. We may want to stop showing the message after a period of time if the user does not verify their email. h2. Functionality Email address changes should not take affect until the address is verified. We will need to store the new email address and only update the official record when the verification link is clicked. This is necessary for security reasons, through 3rd party plugins that may trust the email address and associate it with an external account, like Kayako. A method to check whether an email address has been verified should be available over the API, so such a method should not be private. Plugins may want to check whether an address has been verified, and thus can be trusted. |
It may be necessary to have new customers verify their email address prior to accepting an order or allowing certain functionality through extensions. Blesta core should be aware of and handle email verification, and the order plugin should be able to enforce it.
h2. New Setting Add a new setting for the company and client group to require email verification for new accounts. This would apply to both the client (primary contact) and any other contacts. h2. Email When a contact or client is created in the client group or company, based on the setting, send an email to the contact with a special link that can be used to validate their email address. Track whether an email address has been verified. The link should not have an expiry like password resets. h2. UI If the setting is enabled and the email address has not been verified, display a warning in the client area with an option to resend the verification email. We may want to stop showing the message after a period of time if the user does not verify their email. h2. Functionality Email address changes should not take affect until the address is verified. We will need to store the new email address and only update the official record when the verification link is clicked. This is necessary for security reasons, through 3rd party plugins that may trust the email address and associate it with an external account, like Kayako. A method to check whether an email address has been verified should be available over the API, so such a method should not be private. Plugins may want to check whether an address has been verified, and thus can be trusted. --- See sub-tasks for full/updated details. |
| Description |
It may be necessary to have new customers verify their email address prior to accepting an order or allowing certain functionality through extensions. Blesta core should be aware of and handle email verification, and the order plugin should be able to enforce it.
h2. New Setting Add a new setting for the company and client group to require email verification for new accounts. This would apply to both the client (primary contact) and any other contacts. h2. Email When a contact or client is created in the client group or company, based on the setting, send an email to the contact with a special link that can be used to validate their email address. Track whether an email address has been verified. The link should not have an expiry like password resets. h2. UI If the setting is enabled and the email address has not been verified, display a warning in the client area with an option to resend the verification email. We may want to stop showing the message after a period of time if the user does not verify their email. h2. Functionality Email address changes should not take affect until the address is verified. We will need to store the new email address and only update the official record when the verification link is clicked. This is necessary for security reasons, through 3rd party plugins that may trust the email address and associate it with an external account, like Kayako. A method to check whether an email address has been verified should be available over the API, so such a method should not be private. Plugins may want to check whether an address has been verified, and thus can be trusted. --- See sub-tasks for full/updated details. |
It may be necessary to have new customers verify their email address prior to accepting an order or allowing certain functionality through extensions. Blesta core should be aware of and handle email verification, and the order plugin should be able to enforce it.
h2. New Setting Add a new setting for the company and client group to require email verification for new accounts. This would apply to both the client (primary contact) and any other contacts. h2. Email When a contact or client is created in the client group or company, based on the setting, send an email to the contact with a special link that can be used to validate their email address. Track whether an email address has been verified. The link should not have an expiry like password resets. h2. UI If the setting is enabled and the email address has not been verified, display a warning in the client area with an option to resend the verification email. We may want to stop showing the message after a period of time if the user does not verify their email. h2. Functionality Email address changes should not take affect until the address is verified. We will need to store the new email address and only update the official record when the verification link is clicked. This is necessary for security reasons, through 3rd party plugins that may trust the email address and associate it with an external account, like Kayako. A method to check whether an email address has been verified should be available over the API, so such a method should not be private. Plugins may want to check whether an address has been verified, and thus can be trusted. ---- See sub-tasks for full/updated details. |
| Description |
It may be necessary to have new customers verify their email address prior to accepting an order or allowing certain functionality through extensions. Blesta core should be aware of and handle email verification, and the order plugin should be able to enforce it.
h2. New Setting Add a new setting for the company and client group to require email verification for new accounts. This would apply to both the client (primary contact) and any other contacts. h2. Email When a contact or client is created in the client group or company, based on the setting, send an email to the contact with a special link that can be used to validate their email address. Track whether an email address has been verified. The link should not have an expiry like password resets. h2. UI If the setting is enabled and the email address has not been verified, display a warning in the client area with an option to resend the verification email. We may want to stop showing the message after a period of time if the user does not verify their email. h2. Functionality Email address changes should not take affect until the address is verified. We will need to store the new email address and only update the official record when the verification link is clicked. This is necessary for security reasons, through 3rd party plugins that may trust the email address and associate it with an external account, like Kayako. A method to check whether an email address has been verified should be available over the API, so such a method should not be private. Plugins may want to check whether an address has been verified, and thus can be trusted. ---- See sub-tasks for full/updated details. |
{quote}It may be necessary to have new customers verify their email address prior to accepting an order or allowing certain functionality through extensions. Blesta core should be aware of and handle email verification, and the order plugin should be able to enforce it.
h2. New Setting Add a new setting for the company and client group to require email verification for new accounts. This would apply to both the client (primary contact) and any other contacts. h2. Email When a contact or client is created in the client group or company, based on the setting, send an email to the contact with a special link that can be used to validate their email address. Track whether an email address has been verified. The link should not have an expiry like password resets. h2. UI If the setting is enabled and the email address has not been verified, display a warning in the client area with an option to resend the verification email. We may want to stop showing the message after a period of time if the user does not verify their email. h2. Functionality Email address changes should not take affect until the address is verified. We will need to store the new email address and only update the official record when the verification link is clicked. This is necessary for security reasons, through 3rd party plugins that may trust the email address and associate it with an external account, like Kayako. A method to check whether an email address has been verified should be available over the API, so such a method should not be private. Plugins may want to check whether an address has been verified, and thus can be trusted.{quote} ---- See sub-tasks for full/updated details. |
| Sprint | 4.12.0 Sprint 1 [ 112 ] |
| Rank | Ranked higher |
| Fix Version/s | 4.12.0-b1 [ 11502 ] |
| Sprint | 4.12.0 Sprint 1 [ 112 ] |
| Rank | Ranked lower |
| Fix Version/s | 4.12.0-b1 [ 11502 ] |
| Rank | Ranked higher |
| Assignee | Abdy Franco [ abdy ] |
| Status | Open [ 1 ] | In Progress [ 3 ] |
Automated transition triggered when Abdy Franco created pull request #922 in Stash -
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Sprint | 4.12.0 Sprint 1 [ 112 ] | 4.12.0 Sprint 2 [ 113 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 45 minutes [ 2700 ] | |
| Worklog Id | 13874 [ 13874 ] |
| Time Spent | 45 minutes [ 2700 ] | 2 hours, 55 minutes [ 10500 ] |
| Worklog Id | 13888 [ 13888 ] |
| Time Spent | 2 hours, 55 minutes [ 10500 ] | 4 hours, 43 minutes [ 16980 ] |
| Worklog Id | 13889 [ 13889 ] |
| Time Spent | 4 hours, 43 minutes [ 16980 ] | 4 hours, 50 minutes [ 17400 ] |
| Worklog Id | 13891 [ 13891 ] |
| Time Spent | 4 hours, 50 minutes [ 17400 ] | 5 hours, 11 minutes [ 18660 ] |
| Worklog Id | 13899 [ 13899 ] |
| Sprint | 4.12.0 Sprint 1 [ 113 ] | 4.12.0 Sprint 2 [ 114 ] |
| Rank | Ranked lower |
| Time Spent | 5 hours, 11 minutes [ 18660 ] | 7 hours, 10 minutes [ 25800 ] |
| Worklog Id | 13914 [ 13914 ] |
| Time Spent | 7 hours, 10 minutes [ 25800 ] | 7 hours, 24 minutes [ 26640 ] |
| Worklog Id | 13933 [ 13933 ] |
Automated transition triggered when Jonathan Reissmueller merged pull request #922 in Stash -
| Status | In Review [ 5 ] | Closed [ 6 ] |