{"id":17949,"date":"2016-12-05T21:48:09","date_gmt":"2016-12-05T21:48:09","guid":{"rendered":"https:\/\/developer.kore.com\/?post_type=docs&#038;p=9118"},"modified":"2021-03-18T10:11:31","modified_gmt":"2021-03-18T10:11:31","slug":"setting-up-authorization-using-an-api-key","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v8-1\/docs\/bots\/advanced-topics\/authorization\/setting-up-authorization-using-an-api-key\/","title":{"rendered":"Setting Up Authorization using an API Key"},"content":{"rendered":"<section class=\"l-section wpb_row height_auto\"><div class=\"l-section-h i-cf\"><div class=\"g-cols vc_row type_default valign_top\"><div class=\"vc_col-sm-12 wpb_column vc_column_container\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\">\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<p>An API key can act as both a unique identifier and a secret token for identification as well as authorization 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 Bot.<\/p>\n<p>To use the API Key <strong>Authorization Type<\/strong>, you must first register an account with the web application and then generate an API Key for that application to configure the settings for the Kore.ai authorization mechanism.<\/p>\n<p>To define Authorization for your bot, follow these steps:<\/p>\n<ol>\n<li>Open the bot for which you want to configure an Authorization profile.<\/li>\n<li>Hover over the left-side navigation panel and from <strong>Settings -&gt; Config Settings<\/strong> select <strong>Authorization Profile<\/strong><br \/>\n<a ref=\"magnificPopup\" href=\"\/wp-content\/uploads\/sites\/18\/auth-profiles.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignnone size-full wp-image-21924\" src=\"\/wp-content\/uploads\/sites\/18\/auth-profiles.png\" alt=\"\" width=\"349\" height=\"569\" srcset=\"https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/wp-content\/uploads\/sites\/18\/20221201101820\/auth-profiles.png 349w, https:\/\/kore-wordpress.s3.us-east-2.amazonaws.com\/developer.kore.ai\/wp-content\/uploads\/sites\/18\/20221201101820\/auth-profiles-184x300.png 184w\" sizes=\"auto, (max-width: 349px) 100vw, 349px\" \/><\/a><\/li>\n<li>Click<strong> Add<\/strong>.\u00a0The <strong>New Authorization Mechanism<\/strong> dialog opens.<\/li>\n<li>In the <strong>Authorization Type<\/strong> drop-down list, select\u00a0<strong>Api Key<\/strong>.<\/li>\n<li>The following illustration shows the fields to define for the API Key <strong>Authorization Type<\/strong>.<br \/>\n<a ref=\"magnificPopup\" href=\"\/wp-content\/uploads\/sites\/18\/DIYAPIKey-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-8682 alignnone\" src=\"\/wp-content\/uploads\/sites\/18\/DIYAPIKey-1.png\" alt=\"Authorization Tab - API Key Dialog\" width=\"537\" height=\"982\" \/><\/a><\/li>\n<\/ol>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h2><span class=\"ez-toc-section\" id=\"Defining_Tenancy\">Defining Tenancy<\/span><\/h2>\n<p>If\u00a0required, in the\u00a0<strong>Subdomain<\/strong>\u00a0section, select <strong>Yes<\/strong>\u00a0if the base URL for a web application or user interface the uses a\u00a0tenant name in the URL. For example,\u00a0<span style=\"color: #0000ff\">kore<\/span> is the tenant organization for a web service using tenants at <span style=\"color: #0000ff\">www.<strong><em>kore<\/em><\/strong>.someCompany.com.<\/span><\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h2><span class=\"ez-toc-section\" id=\"Adding_Authorization_Fields\"><span class=\"wysiwyg-font-size-large\">Adding Authorization Fields<\/span><\/span><\/h2>\n<p>By default, authorization fields are configured as part of the header of the Bot\u00a0request message. If your Bot\u00a0request requires additional authorization fields or the expected authorization is not part of the header, for example, social security number or PIN, click <strong>Add<\/strong>\u00a0in the <strong>Authorization Fields<\/strong> section and then define the fields as shown in the following illustration.<br \/>\n<a ref=\"magnificPopup\" href=\"\/wp-content\/uploads\/sites\/18\/DIYBasicAuthAddAuthField.png\"><img loading=\"lazy\" decoding=\"async\" class=\"wp-image-8667 size-full alignnone\" src=\"\/wp-content\/uploads\/sites\/18\/DIYBasicAuthAddAuthField.png\" alt=\"Adding an Auth Field for Basic Auth\" width=\"590\" height=\"618\" \/><\/a><\/p>\n<ol>\n<li>In the <strong>Field Type<\/strong> field, you can select one of the following depending on where in the Bot\u00a0request message and the type of authorization fields that are required.\n<ul>\n<li><strong>Header<\/strong> &#8211;\u00a0The Bot\u00a0expects the authorization fields as part of the header\u00a0of the request.<\/li>\n<li><strong>Payload<\/strong> &#8211; The Bot\u00a0expects the authorization fields as part of the content of the body of the request.<\/li>\n<li><strong>Query String<\/strong> &#8211;\u00a0The Bot\u00a0expects the authorization fields as a query in the body\u00a0of the request.<\/li>\n<li><strong>Path Param<\/strong> &#8211; The Bot expects the authorization fields as part of the URL path for the request.<\/li>\n<\/ul>\n<\/li>\n<li>In the <strong>Field Key<\/strong> field, enter the name of the field for the selected <strong>Field Type<\/strong>.<\/li>\n<li>In the <strong>Field Value<\/strong> field,\u00a0enter the value for the <strong>Field Key<\/strong> specified.<\/li>\n<li>Click <strong>Add<\/strong>. The new authorization field is added in the <strong>Authorization Fields<\/strong> section.<\/li>\n<\/ol>\n<p>To add additional authorization fields, click <strong>Add<\/strong>\u00a0in the <strong>Authorization\u00a0Fields<\/strong> section.<\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h2><span class=\"ez-toc-section\" id=\"Adding_IDP_Form_Fields\"><span class=\"wysiwyg-font-size-large\">Adding IDP Form Fields<\/span><\/span><\/h2>\n<p>If the default username and password fields do not meet your needs, you can add new\u00a0fields displayed to the end-user by adding authorization IDP form fields. To add fields\u00a0on the authorization form, click <strong>Add<\/strong>\u00a0in the <strong>IDP Form Fields<\/strong> section.<\/p>\n<p>The following table describes the fields used to define an authorization IDP form field.<\/p>\n<table>\n<thead>\n<tr>\n<th class=\"wysiwyg-text-align-left\" scope=\"col\">FIELD NAME<\/th>\n<th class=\"wysiwyg-text-align-left\">DESCRIPTION<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Title of Field<\/td>\n<td>Specify the name of the field\u00a0displayed to the end-user in the authentication dialog.<\/td>\n<\/tr>\n<tr>\n<td>Field Key<\/td>\n<td>The value represents the end-user input value to the authenticating service.<\/td>\n<\/tr>\n<tr>\n<td>Help Hint<\/td>\n<td>The help text displayed in the field to describe what should be entered into the field.<\/td>\n<\/tr>\n<tr>\n<td>Field Type<\/td>\n<td>When <strong>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 <strong>Field Key<\/strong>, one of:<\/p>\n<ul>\n<li><strong>Textbox<\/strong><\/li>\n<li><strong>Password<\/strong><\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<tr>\n<td>Mandatory<\/td>\n<td>When <strong>Advanced Options<\/strong> is selected, select if the end-user must define this field to complete authentication.<\/td>\n<\/tr>\n<tr>\n<td>Data Type<\/td>\n<td>When <strong>Advanced Options<\/strong> is selected, specify the type of data expected as input from the end-user, for example, <strong>String<\/strong>.<\/td>\n<\/tr>\n<tr>\n<td>Visibility<\/td>\n<td>When <strong>Advanced Options<\/strong> is selected, specify if the authentication field should be visible, hidden, or displayed as read-only.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h2><span class=\"ez-toc-section\" id=\"Authorization_Check_URL\">Authorization Check URL<\/span><\/h2>\n<p>In the <strong>Authorization Check URL<\/strong> field, optionally define a URL that can be used to test the authentication settings from Bot\u00a0Builder before you deploy the Bot\u00a0with the authorization mechanism. You can use dynamic fields, path parameter fields, query fields, and so forth, to define the test URL, for example,<br \/>\n<span style=\"color: #0000ff\">https:\/\/kore.someCompany.com\/sap\/opu\/odata\/sap\/{{authfield1}}\/?$format=json<\/span><\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h2><span class=\"ez-toc-section\" id=\"Access_Using_a_Connector\">Access Using a Connector<\/span><\/h2>\n<p>In the <strong>Access Using a Connector<\/strong> section, select <strong>Yes<\/strong> to enable access for Kore.ai Bots using the Kore.ai Connector agent. If your domain does not have any active Kore.ai Connectors defined, a warning message is displayed to contact the Bots Admin Console system, administrator. For more information, see <a href=\"\/v8-1\/docs\/bots\/adminconsole\/security\/using-the-kore-connector\/\">Using the Kore.ai Connector<\/a>\u00a0in the Bots Admin Console documentation.<\/p>\n<p>Click <strong>Save<\/strong>\u00a0to save the authorization settings and close the <strong>New Authorization Mechanism<\/strong> dialog.<\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div>\r\n\t<div class=\"wpb_text_column \">\r\n\t\t<div class=\"wpb_wrapper\">\r\n\t\t\t<h2><span class=\"ez-toc-section\" id=\"Testing_the_Authorization\"><span class=\"wysiwyg-font-size-large\">Testing the Authorization<\/span><\/span><\/h2>\n<p>After you save the authentication, you can test your authorization definition when you click <strong>Test <\/strong>from the Authorization Profile page.<\/p>\n<p>When you\u00a0click <strong>Test<\/strong>, the <strong>Test Authorization<\/strong> dialog is displayed.<br \/>\n<a ref=\"magnificPopup\" href=\"\/wp-content\/uploads\/sites\/18\/DIYTestAuthorizationDialogAPIKey.png\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-8683 alignnone\" src=\"\/wp-content\/uploads\/sites\/18\/DIYTestAuthorizationDialogAPIKey.png\" alt=\"Test Authorization - API Key\" width=\"594\" height=\"568\" \/><\/a><br \/>\n<strong>To configure the Test Authorization &#8211;\u00a0API Key<\/strong><\/p>\n<ol>\n<li>In the <strong>Auth Check URL<\/strong> field, verify or enter the URL to test the authentication configuration.<\/li>\n<li>If your bot uses subdomains, the <strong>Tenancy<\/strong> field is displayed and you must specify the tenant.<\/li>\n<li>Enter the API key for the application in the <strong>API Key<\/strong> field.<\/li>\n<li>Select the content type expected for the URL in the <strong>Content-Type<\/strong> field.<\/li>\n<li>For testing the URL, the <strong>Method<\/strong>\u00a0field is read-only and set to <strong>GET<\/strong>.<\/li>\n<li>Click <strong>Test<\/strong> to begin the authorization test.<\/li>\n<\/ol>\n<p>When the validation of authentication is complete, the <strong>Test Authorization<\/strong> dialog is closed and the results of the validation, either success or failure, is displayed to the immediate right of the <strong>Test Authorization<\/strong> button. If the authorization fails, the <em>Auth Test Failed<\/em> message is displayed along with the <strong>Headers<\/strong> and <strong>Response<\/strong> tabs as shown in the following illustration.<br \/>\n<a ref=\"magnificPopup\" href=\"\/wp-content\/uploads\/sites\/18\/DIYTestAuthorizationDialogFail.png\"><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-8684\" src=\"\/wp-content\/uploads\/sites\/18\/DIYTestAuthorizationDialogFail.png\" alt=\"Test Authorization Failure Dialog\" width=\"595\" height=\"473\" \/><\/a><\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n<div class=\"w-separator size_small with_line width_default thick_1 style_solid color_border align_center\"><div class=\"w-separator-h\"><\/div><\/div><\/div><\/div><\/div><\/div><\/div><\/section>\n","protected":false},"excerpt":{"rendered":"An API key can act as both a unique identifier and a secret token for identification as well as authorization 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...","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[],"class_list":["post-17949","post","type-post","status-publish","format-standard","hentry","category-authorization"],"_links":{"self":[{"href":"https:\/\/developer.kore.ai\/v8-1\/wp-json\/wp\/v2\/posts\/17949","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/developer.kore.ai\/v8-1\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/developer.kore.ai\/v8-1\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v8-1\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/developer.kore.ai\/v8-1\/wp-json\/wp\/v2\/comments?post=17949"}],"version-history":[{"count":5,"href":"https:\/\/developer.kore.ai\/v8-1\/wp-json\/wp\/v2\/posts\/17949\/revisions"}],"predecessor-version":[{"id":21940,"href":"https:\/\/developer.kore.ai\/v8-1\/wp-json\/wp\/v2\/posts\/17949\/revisions\/21940"}],"wp:attachment":[{"href":"https:\/\/developer.kore.ai\/v8-1\/wp-json\/wp\/v2\/media?parent=17949"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/developer.kore.ai\/v8-1\/wp-json\/wp\/v2\/categories?post=17949"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/developer.kore.ai\/v8-1\/wp-json\/wp\/v2\/tags?post=17949"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}