{"id":45771,"date":"2022-09-28T06:53:36","date_gmt":"2022-09-28T05:53:36","guid":{"rendered":"https:\/\/developer.kore.ai\/v10-1\/?p=45771"},"modified":"2022-09-28T06:53:37","modified_gmt":"2022-09-28T05:53:37","slug":"alert-task-oauth-v2-client-credentials","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v10-1\/uncategorised\/alert-task-oauth-v2-client-credentials\/","title":{"rendered":"Alert Task \u2013 OAuth v2 Client Credentials"},"content":{"rendered":"

We have seen how an Alert Task can be set up in the Kore.ai XO Platform <\/span>here<\/span><\/a>. In this article, we will see how authorization for alert tasks can be set up using the OAuth v2 with client credentials.<\/span><\/p>\n

<\/div><\/div>\n

General Setup<\/span><\/span><\/h1>\n

OAuth v2 is the new version of the open protocol to allow secure authorization in a simple and standard method from web, mobile, and desktop applications. To use oAuth v2, you must first register an account with the web application as you will need the log-in credentials for that application to configure the settings for the Authorization Mechanism.<\/span><\/p>\n

To begin your configuration, follow the steps below:<\/span><\/p>\n

    \n
  1. Select the <\/span>VA <\/strong>you want to work with.<\/span><\/li>\n
  2. Go to <\/span>Build > Conversation Skills > Alert Tasks<\/strong>. <\/span><\/li>\n
  3. Select the <\/span>task <\/strong>you want to work with. <\/span><\/li>\n
  4. Click the <\/span>API Request<\/strong> tab within the Alert Task.<\/span><\/li>\n
  5. Expand the <\/span>Authorization <\/strong>section and click <\/span>Create New<\/strong> to configure a new authorization. 
    \"\"<\/a><\/span><\/li>\n
  6. Next, the New Authorization Mechanism<\/strong> window opens, as shown in the illustration below. 
    \"\"<\/a><\/li>\n<\/ol>\n

    To define a custom authorization, select <\/span>oAuth v2 client credentials<\/strong> in the <\/span>Authorization Type<\/strong> field, then configure each section as explained in the table below:<\/span><\/p>\n\n\n\n\n\n\n\n\n\n\n\n
    \n

    FIELD NAME<\/strong><\/p>\n<\/th>\n

    		\n

    DESCRIPTION<\/strong><\/p>\n<\/th>\n<\/tr>\n

    \n

    Authorization Type<\/span><\/p>\n<\/td>\n

    		\n

    Set to oAuth v2 Client Credentials.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

    Identity Provider Name<\/span><\/p>\n<\/td>\n

    		\n

    The name of the web application or web service, for example, <\/span>Asana<\/span><\/em>. This field is required.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

    Client ID<\/span><\/p>\n<\/td>\n

    		\n

    The ID of the Kore.ai client.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

    Client Secret Key<\/span><\/p>\n<\/td>\n

    		\n

    The value provided as the XO Platform authentication based on the Client ID to the web application.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

    Token Request URL<\/span><\/p>\n<\/td>\n

    		\n

    The URL used by the XO Platform to obtain an unauthorized request token. A request token is a value used by the XO Platform to obtain authorization from the end-user to obtain an access token. After end-user authorization, an access token can be requested by the XO Platform. This field is required.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

    Scope<\/span><\/p>\n<\/td>\n

    		\n

    If the web service requires additional values for authorization, add one or more Key\/Value pairs. For example, some Bot web services support using a scope key using read-only, write, or both as the value.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

    Refresh Token URL<\/span><\/p>\n<\/td>\n

    		\n

    Enter a Refresh Token URL, if required, for cases when the authentication token expires and has to be refreshed. Please see below for details.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

    Description<\/span><\/p>\n<\/td>\n

    		\n

    Enter a description for your authorization. <\/span><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    <\/div><\/div>\n

    Authorization<\/span><\/span><\/h1>\n

    By default, authorization fields are configured as part of the header of the task request message. If your task request requires additional authorization fields or the expected authorization is not part of the header, for example, a verification code, click<\/span> + Add Authorization Field <\/strong>and then define the fields as shown in the following illustration. <\/span><\/p>\n

    \"\"<\/a><\/p>\n

      \n
    1. In the <\/span>Field Type<\/strong> field, you can select one of the following depending on where in the task request message and the type of authorization fields that are required.<\/span><\/li>\n
        \n
      1. Header<\/strong> – The VA expects the authorization fields as part of the header of the request.<\/span><\/li>\n
      2. Payload<\/strong> – The VA expects the authorization fields as part of the content of the body of the request.<\/span><\/li>\n
      3. Query String<\/strong> – The VA expects the authorization fields as a query in the body of the request.<\/span><\/li>\n
      4. Path Param<\/strong> – The VA expects the authorization fields as part of the URL path for the request.<\/span><\/li>\n<\/ol>\n
      5. In the <\/span>Field Key<\/strong> field, enter the name of the field for the selected <\/span>Field Type<\/strong>.<\/span><\/li>\n
      6. In the <\/span>Field Value<\/strong> field, enter the value for the <\/span>Field Key<\/strong> specified.<\/span><\/li>\n
      7. Click <\/span>Done<\/strong>. The new authorization field is added in the <\/span>Authorization Fields<\/strong> section.
        <\/span><\/li>\n<\/ol>\n

        Click <\/span>Save Auth<\/strong> to save the authorization settings and close the <\/span>New Authorization Mechanism<\/strong> dialog.<\/span><\/p>\n

        <\/div><\/div>\n

        Testing<\/span><\/span><\/h1>\n

        After you save the authorization, you can test it using the <\/span>Authorization<\/strong> page.<\/span><\/p>\n

          \n
        1. Click <\/span>Test Authorization<\/strong> before continuing to develop the remaining steps of your task.<\/span>\"\"<\/a><\/li>\n
        2. After you click <\/span>Test Authorization<\/strong>, the test is executed using the authentication token URLs and the <\/span>Client ID<\/strong> and <\/span>Client Secret Key<\/strong>. If the tenancy was defined, the <\/span>Test Authorization<\/strong> window is displayed as shown in the following illustration.<\/span>
          <\/span><\/li>\n
        3. Click <\/span>Test<\/strong> to begin the authorization test. When the validation of authentication is complete, the <\/span>Test Authorization<\/strong> window is closed and the results of the validation, either success or failure, is displayed to the immediate right of the <\/span>Test Authorization<\/strong> button. If the authorization fails, the <\/span>Auth Test Failed<\/span><\/em> message is displayed along with the <\/span>Headers<\/strong> and <\/span>Response<\/strong> tabs as shown in the following illustration.<\/span>
          <\/span><\/li>\n<\/ol>\n
            \n
              <\/ol<\/ol>\n<\/ol>\n

              \"\"<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

              We have seen how an Alert Task can be set up in the Kore.ai XO Platform here. In this article, we will see how authorization for alert tasks can be set up using the OAuth v2 with client credentials. General Setup OAuth v2 is the new version of the open protocol to allow secure authorization…<\/p>\n","protected":false},"author":27,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-45771","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts\/45771","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/users\/27"}],"replies":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/comments?post=45771"}],"version-history":[{"count":1,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts\/45771\/revisions"}],"predecessor-version":[{"id":45793,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/posts\/45771\/revisions\/45793"}],"wp:attachment":[{"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/media?parent=45771"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/categories?post=45771"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-1\/wp-json\/wp\/v2\/tags?post=45771"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}