{"id":27046,"date":"2021-03-17T06:05:43","date_gmt":"2021-03-17T06:05:43","guid":{"rendered":"https:\/\/developer.kore.ai\/v10-2\/?p=27046"},"modified":"2022-09-28T08:29:12","modified_gmt":"2022-09-28T07:29:12","slug":"alert-task-api-key-authorization","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v10-2\/docs\/bots\/bot-builder-tool\/alert\/alert-task-api-key-authorization\/","title":{"rendered":"Alert Task \u2013 Authorization using API Key"},"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 section, we will see how to configure API authorization.<\/span><\/p>\n

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

API Key Setup Overview<\/span><\/span><\/h1>\n

An API key can act as both a unique identifier and a secret token for identification as well as authentication to provide a set of access rights on the associated API. Instead of prompting the end-user for both a username and password for access, the user is prompted only for an API key when configuring the task. To use the API Key <\/span>Authorization Type<\/strong>, you must first register an account with the web application you want to work with, and then generate an API Key for that application<\/span><\/p>\n

To authorize an API key,<\/span><\/p>\n

    \n
  1. Go to Alert Tasks and create or select the task <\/strong>you want to work with. <\/span><\/li>\n
  2. Under <\/span>API Request<\/span><\/em>, expand <\/span>Authorization<\/strong>.<\/span><\/li>\n
  3. Select the <\/span>Authorization PRovider<\/strong>. If none is available, create it by clicking on <\/span>Create New.<\/strong>
    <\/strong>    \"\"<\/a><\/li>\n
  4. Ensure that your selected Authorization Type is <\/span>API Key<\/strong>. Below is an illustration of the fields that you will need to provide information for in order to authorize the API.
    <\/span>    \"\"<\/a><\/li>\n
  5. Name your API<\/strong> to get started, then let us go through these fields in detail.<\/span><\/li>\n<\/ol>\n

    <\/div><\/div><\/span><\/p>\n

    Tenancy<\/span><\/span><\/h1>\n

    If required, in the <\/span>Subdomain<\/strong> section, select <\/span>Yes<\/strong> if the base URL for a web application or user interface uses a tenant name in the URL. For example, <\/span>kore<\/span> is the tenant organization for a web service using tenants as <\/span>www.<\/span>kore<\/em><\/strong>.someCompany.com<\/span>. <\/span><\/p>\n

    In the following example configuration, the tenancy URL contains the <\/span>{tenant}<\/span> organization placeholder, where [tenant] including the braces represents the tenant name.<\/span><\/p>\n

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

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

    Form Fields<\/span><\/span><\/h1>\n

    If the default username and password fields do not meet your needs, you can add new fields displayed to the end-user by adding authorization form fields,  for example, if a PIN code is required in the authentication process, in addition to the Username and Password form fields.<\/span><\/p>\n

    To add fields on the authorization form,Click <\/span>+ Add Form Field. <\/strong><\/p>\n

    The following illustration is an example of a definition to add a password field to the authorization dialog.<\/span><\/p>\n

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

     <\/p>\n

    The following table describes the fields used to define an authorization IDP form field.<\/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<\/thead>\n

    \n

    Title of Field<\/span><\/p>\n<\/td>\n

    		\n

    Specify the name of the field displayed to the end-user in the authentication dialog.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

    Field Key<\/span><\/p>\n<\/td>\n

    		\n

    The value represents the end-user input value to the authenticating service.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

    Help Hint<\/span><\/p>\n<\/td>\n

    		\n

    The help text displayed in the field to describe what should be entered into the field.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

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

    		\n

    When <\/span>Advanced Options<\/strong> is selected, specify the type of field displayed in the end-user interface to collect the user input assigned as the value for the <\/span>Field Key<\/strong>, one of:<\/span><\/p>\n

      \n
    • Textbox<\/strong><\/li>\n
    • Password<\/strong><\/li>\n<\/ul>\n<\/td>\n<\/tr>\n
    \n

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

    		\n

    When <\/span>Advanced Options<\/strong> is selected, select if the end-user must define this field to complete authentication.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

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

    		\n

    When <\/span>Advanced Options<\/strong> is selected, specify the type of data expected as input from the end-user, for example, <\/span>String<\/strong>.<\/span><\/p>\n<\/td>\n<\/tr>\n

    \n

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

    		\n

    When <\/span>Advanced Options<\/strong> is selected, specify if the authentication field should be visible, hidden, or displayed as read-only.<\/span><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

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

    Authorization Fields<\/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, social security number or PIN,<\/span><\/p>\n

      \n
    1. Click <\/span>+ Add Authorization Field<\/strong> and then define the fields as shown in the following illustration.<\/span>
      <\/span>\"\"<\/a><\/li>\n
    2. 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>
      <\/span>Header<\/strong> – The VA expects the authorization fields as part of the header of the request.<\/span>Payload<\/strong> – The VA expects the authorization fields as part of the content of the body of the request.<\/span>Query String<\/strong> – The VA expects the authorization fields as a query in the body of the request.<\/span>Path Param<\/strong> – The VA expects the authorization fields as part of the URL path for the request.<\/span><\/li>\n
    3. In the <\/span>Field Key<\/strong> field, enter the name of the field for the selected <\/span>Field Type<\/strong>.<\/span><\/li>\n
    4. In the <\/span>Field Value<\/strong> field, enter the value for the <\/span>Field Key<\/strong> specified.<\/span><\/li>\n
    5. Click <\/span>Add<\/strong>. The new authorization field is added in the <\/span>Authorization Fields<\/strong> section.<\/span><\/li>\n
    6. To add additional authorization fields, click <\/span>Add<\/strong> in the <\/span>Authorization Fields<\/strong> section.<\/span><\/li>\n
    7. Click <\/span>Save<\/strong> Auth <\/strong>to save the authorization settings and close the <\/span>New Authorization Mechanism<\/strong> dialog.<\/span><\/li>\n<\/ol>\n

      <\/div><\/div><\/span><\/p>\n

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

      After you save the authentication, if you have defined an <\/span>Authorization Check URL<\/strong> for your new authorization type, you can test your authorization definition on the <\/span>Authentication<\/strong> tab when you click <\/span>Test Authorization<\/strong> before continuing to develop the remaining steps of your task.<\/span><\/p>\n

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

      After you click <\/span>Test Authorization<\/strong>, the <\/span>Test Authorization<\/strong> window is displayed and populated with the URL you specified in the <\/span>Authorization Check URL<\/strong> section, as shown in the following illustration.<\/span><\/p>\n

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

      To configure the Test Authorization – API Key<\/span><\/p>\n

        \n
      1. In the <\/span>Auth Check URL<\/strong> field, verify or enter the URL to test the authentication configuration.<\/span><\/li>\n
      2. If your VA uses subdomains, the <\/span>Tenancy<\/strong> field is displayed and you must specify the tenant.<\/span><\/li>\n
      3. Enter the API key for the application in the <\/span>API Key<\/strong> field.<\/span><\/li>\n
      4. Select the content type expected for the URL in the <\/span>Content-Type<\/strong> field.<\/span><\/li>\n
      5. For testing the URL, the <\/span>Method<\/strong> field is read-only and set to <\/span>GET<\/strong>.<\/span><\/li>\n
      6. Click <\/span>Test<\/strong> to begin the authorization test.<\/span><\/li>\n<\/ol>\n

        When the authentication validation is complete, the <\/span>Test Authorization<\/strong> dialog is closed and the results of the validation, either success or failure, are 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><\/p>\n

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

        <\/div><\/div>\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 section, we will see how to configure API authorization. API Key Setup Overview An API key can act as both a unique identifier and a secret token for identification as well as authentication to provide a…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[67],"tags":[],"class_list":["post-27046","post","type-post","status-publish","format-standard","hentry","category-alert"],"_links":{"self":[{"href":"https:\/\/developer.kore.ai\/v10-2\/wp-json\/wp\/v2\/posts\/27046","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/developer.kore.ai\/v10-2\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/developer.kore.ai\/v10-2\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-2\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-2\/wp-json\/wp\/v2\/comments?post=27046"}],"version-history":[{"count":3,"href":"https:\/\/developer.kore.ai\/v10-2\/wp-json\/wp\/v2\/posts\/27046\/revisions"}],"predecessor-version":[{"id":45891,"href":"https:\/\/developer.kore.ai\/v10-2\/wp-json\/wp\/v2\/posts\/27046\/revisions\/45891"}],"wp:attachment":[{"href":"https:\/\/developer.kore.ai\/v10-2\/wp-json\/wp\/v2\/media?parent=27046"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-2\/wp-json\/wp\/v2\/categories?post=27046"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/developer.kore.ai\/v10-2\/wp-json\/wp\/v2\/tags?post=27046"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}