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

Support Manager: Add reCaptcha option for tickets opened publicly

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.4.0-b1
    • Fix Version/s: 4.12.0-b1
    • Component/s: Plugins
    • Labels:
      None

      Description

      Public ticket pages often get spammed.

      The order system allows reCaptcha to be used so when clients are registered there is some form of human verification. Let's add this option to Support Departments also.

      There was some thoughts of making reCaptcha a company setting, to be used by extensions.. but unless we do that users will just be able to define this in the order system and support departments independently.

      There is now a Human Verification option in the core under Settings > Company > General > Human Verification, so all we have to do is have an option to "Enable Human Verification" on the support department

      Add a "Human Verification" drop down when creating/editing support departments.
      None
      reCaptcha

      When selecting reCaptcha, display 2 text fields:
      reCaptcha Site Key
      reCaptcha Shared Key

      Maybe we should add an additional option so the Captcha is only shown if the user is unauthenticated. Then it would appear only if "Allow only clients to open or reply to tickets" is unchecked, and the client was not logged in.

        Issue Links

          Activity

          admin Paul Phillips created issue -
          tyson Tyson Phillips (Inactive) made changes -
          Field Original Value New Value
          Link This issue is blocked by CORE-2895 [ CORE-2895 ]
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked higher
          tyson Tyson Phillips (Inactive) made changes -
          Rank Ranked lower
          tyson Tyson Phillips (Inactive) made changes -
          Issue Type Bug [ 1 ] Improvement [ 4 ]
          admin Paul Phillips made changes -
          Rank Ranked higher
          admin Paul Phillips made changes -
          Description Public ticket pages often get spammed.

          The order system allows reCaptcha to be used so when clients are registered there is some form of human verification. Let's add this option to Support Departments also.

          There was some thoughts of making reCaptcha a company setting, to be used by extensions.. but unless we do that users will just be able to define this in the order system and support departments independently.

          Add a "Human Verification" drop down when creating/editing support departments.
          * None
          * reCaptcha

          When selecting reCaptcha, display 2 text fields:
          * reCaptcha Site Key
          * reCaptcha Shared Key

          Maybe we should add an additional option so the Captcha is only shown if the user is unauthenticated. Then it would appear only if "Allow only clients to open or reply to tickets" is unchecked, and the client was not logged in.
          Public ticket pages often get spammed.

          The order system allows reCaptcha to be used so when clients are registered there is some form of human verification. Let's add this option to Support Departments also.

          There was some thoughts of making reCaptcha a company setting, to be used by extensions.. but unless we do that users will just be able to define this in the order system and support departments independently.

          *There is now a Human Verification option in the core under Settings > Company > General > Human Verification, so all we have to do is have an option to "Enable Human Verification" on the support department*

          -Add a "Human Verification" drop down when creating/editing support departments.
          * None
          * reCaptcha

          When selecting reCaptcha, display 2 text fields:
          * reCaptcha Site Key
          * reCaptcha Shared Key-

          Maybe we should add an additional option so the Captcha is only shown if the user is unauthenticated. Then it would appear only if "Allow only clients to open or reply to tickets" is unchecked, and the client was not logged in.
          admin Paul Phillips made changes -
          Description Public ticket pages often get spammed.

          The order system allows reCaptcha to be used so when clients are registered there is some form of human verification. Let's add this option to Support Departments also.

          There was some thoughts of making reCaptcha a company setting, to be used by extensions.. but unless we do that users will just be able to define this in the order system and support departments independently.

          *There is now a Human Verification option in the core under Settings > Company > General > Human Verification, so all we have to do is have an option to "Enable Human Verification" on the support department*

          -Add a "Human Verification" drop down when creating/editing support departments.
          * None
          * reCaptcha

          When selecting reCaptcha, display 2 text fields:
          * reCaptcha Site Key
          * reCaptcha Shared Key-

          Maybe we should add an additional option so the Captcha is only shown if the user is unauthenticated. Then it would appear only if "Allow only clients to open or reply to tickets" is unchecked, and the client was not logged in.
          Public ticket pages often get spammed.

          The order system allows reCaptcha to be used so when clients are registered there is some form of human verification. Let's add this option to Support Departments also.

          There was some thoughts of making reCaptcha a company setting, to be used by extensions.. but unless we do that users will just be able to define this in the order system and support departments independently.

          *There is now a Human Verification option in the core under Settings > Company > General > Human Verification, so all we have to do is have an option to "Enable Human Verification" on the support department*

          -Add a "Human Verification" drop down when creating/editing support departments. -
          -* None-
          -* reCaptcha-

          -When selecting reCaptcha, display 2 text fields:-
          -* reCaptcha Site Key-
          -* reCaptcha Shared Key-

          Maybe we should add an additional option so the Captcha is only shown if the user is unauthenticated. Then it would appear only if "Allow only clients to open or reply to tickets" is unchecked, and the client was not logged in.
          admin Paul Phillips made changes -
          Description Public ticket pages often get spammed.

          The order system allows reCaptcha to be used so when clients are registered there is some form of human verification. Let's add this option to Support Departments also.

          There was some thoughts of making reCaptcha a company setting, to be used by extensions.. but unless we do that users will just be able to define this in the order system and support departments independently.

          *There is now a Human Verification option in the core under Settings > Company > General > Human Verification, so all we have to do is have an option to "Enable Human Verification" on the support department*

          -Add a "Human Verification" drop down when creating/editing support departments. -
          -* None-
          -* reCaptcha-

          -When selecting reCaptcha, display 2 text fields:-
          -* reCaptcha Site Key-
          -* reCaptcha Shared Key-

          Maybe we should add an additional option so the Captcha is only shown if the user is unauthenticated. Then it would appear only if "Allow only clients to open or reply to tickets" is unchecked, and the client was not logged in.
          Public ticket pages often get spammed.

          The order system allows reCaptcha to be used so when clients are registered there is some form of human verification. Let's add this option to Support Departments also.

          There was some thoughts of making reCaptcha a company setting, to be used by extensions.. but unless we do that users will just be able to define this in the order system and support departments independently.

          *There is now a Human Verification option in the core under Settings > Company > General > Human Verification, so all we have to do is have an option to "Enable Human Verification" on the support department*

          -Add a "Human Verification" drop down when creating/editing support departments. -
          -None-
          -reCaptcha-

          -When selecting reCaptcha, display 2 text fields:-
          -reCaptcha Site Key-
          -reCaptcha Shared Key-

          Maybe we should add an additional option so the Captcha is only shown if the user is unauthenticated. Then it would appear only if "Allow only clients to open or reply to tickets" is unchecked, and the client was not logged in.
          admin Paul Phillips made changes -
          Description Public ticket pages often get spammed.

          The order system allows reCaptcha to be used so when clients are registered there is some form of human verification. Let's add this option to Support Departments also.

          There was some thoughts of making reCaptcha a company setting, to be used by extensions.. but unless we do that users will just be able to define this in the order system and support departments independently.

          *There is now a Human Verification option in the core under Settings > Company > General > Human Verification, so all we have to do is have an option to "Enable Human Verification" on the support department*

          -Add a "Human Verification" drop down when creating/editing support departments. -
          -None-
          -reCaptcha-

          -When selecting reCaptcha, display 2 text fields:-
          -reCaptcha Site Key-
          -reCaptcha Shared Key-

          Maybe we should add an additional option so the Captcha is only shown if the user is unauthenticated. Then it would appear only if "Allow only clients to open or reply to tickets" is unchecked, and the client was not logged in.
          Public ticket pages often get spammed.

          The order system allows reCaptcha to be used so when clients are registered there is some form of human verification. Let's add this option to Support Departments also.

          There was some thoughts of making reCaptcha a company setting, to be used by extensions.. but unless we do that users will just be able to define this in the order system and support departments independently.

          *There is now a Human Verification option in the core under Settings > Company > General > Human Verification, so all we have to do is have an option to "Enable Human Verification" on the support department*

          -Add a "Human Verification" drop down when creating/editing support departments.-
          -None-
          -reCaptcha-

          -When selecting reCaptcha, display 2 text fields:-
          -reCaptcha Site Key-
          -reCaptcha Shared Key-

          Maybe we should add an additional option so the Captcha is only shown if the user is unauthenticated. Then it would appear only if "Allow only clients to open or reply to tickets" is unchecked, and the client was not logged in.
          admin Paul Phillips made changes -
          Rank Ranked higher
          Hide
          jonathan Jonathan Reissmueller added a comment -

          This should have no effect on email tickets, staff can configure the department to reject email tickets if they wish

          Show
          jonathan Jonathan Reissmueller added a comment - This should have no effect on email tickets, staff can configure the department to reject email tickets if they wish
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked higher
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked lower
          jonathan Jonathan Reissmueller made changes -
          Fix Version/s 4.12.0-b1 [ 11502 ]
          Fix Version/s Short Term [ 10800 ]
          jonathan Jonathan Reissmueller made changes -
          Story Points 3
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked higher
          jonathan Jonathan Reissmueller made changes -
          Sprint 4.12.0 Sprint 3 [ 115 ]
          jonathan Jonathan Reissmueller made changes -
          Rank Ranked lower
          jonathan Jonathan Reissmueller made changes -
          Assignee Jonathan Reissmueller [ jonathan ]
          Automated transition triggered when Jonathan Reissmueller created a branch in Stash -
          Status Open [ 1 ] In Progress [ 3 ]
          jonathan Jonathan Reissmueller made changes -
          Remaining Estimate 0 minutes [ 0 ]
          Time Spent 1 hour, 53 minutes [ 6780 ]
          Worklog Id 14008 [ 14008 ]
          Automated transition triggered when Jonathan Reissmueller created pull request #85 in Stash -
          Status In Progress [ 3 ] In Review [ 5 ]
          Resolution Fixed [ 1 ]
          abdy Abdy Franco made changes -
          Time Spent 1 hour, 53 minutes [ 6780 ] 3 hours [ 10800 ]
          Worklog Id 14011 [ 14011 ]
          abdy Abdy Franco made changes -
          Time Spent 3 hours [ 10800 ] 3 hours, 11 minutes [ 11460 ]
          Worklog Id 14014 [ 14014 ]
          Automated transition triggered when Jonathan Reissmueller merged pull request #85 in Stash -
          Status In Review [ 5 ] Closed [ 6 ]

            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:
                17/Sep/20

                Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0 minutes
                0m
                Logged:
                Time Spent - 3 hours, 11 minutes
                3h 11m

                  Agile