{"id":17946,"date":"2016-12-05T21:43:32","date_gmt":"2016-12-05T21:43:32","guid":{"rendered":"https:\/\/developer.kore.com\/?post_type=docs&p=9111"},"modified":"2021-03-18T10:14:47","modified_gmt":"2021-03-18T10:14:47","slug":"setting-up-authorization-using-oauth-v2-password-grant","status":"publish","type":"post","link":"https:\/\/developer.kore.ai\/v8-1\/docs\/bots\/advanced-topics\/authorization\/setting-up-authorization-using-oauth-v2-password-grant\/","title":{"rendered":"Setting Up Authorization using oAuth v2 password grant"},"content":{"rendered":"
\r\n\t
\r\n\t\t
\r\n\t\t\t

To define Authorization for your bot, follow these steps:<\/p>\n

    \n
  1. Open the bot for which you want to configure an Authorization profile.<\/li>\n
  2. Hover over the left-side navigation panel and from Settings -> Config Settings<\/strong> select Authorization Profile<\/strong>
    \n\"\"<\/a><\/li>\n
  3. Click Add<\/strong>.\u00a0The New Authorization Mechanism<\/strong> dialog opens.<\/li>\n
  4. In the Authorization Type<\/strong> drop-down list, select oAuth v2 password grant type<\/strong>.<\/li>\n
  5. The following illustration is an example of the oAuth v2 password grant<\/strong> authorization type fields that you must define to enable a customized authorization for your Bot.
    \n    \"\"<\/a><\/li>\n<\/ol>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n
    <\/div><\/div>\r\n\t
    \r\n\t\t
    \r\n\t\t\t

    Defining Tenancy<\/span><\/h3>\n

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

    In the following example configuration, the tenancy URL contains the {tenant}<\/span> organization placeholder.<\/p>\n

    \"\"<\/a><\/p>\n\r\n\t\t<\/div>\r\n\t<\/div>\r\n

    <\/div><\/div>\r\n\t
    \r\n\t\t
    \r\n\t\t\t

    Adding Authorization Fields<\/span><\/span><\/h3>\n

    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 Add<\/strong>\u00a0in the Authorization Fields<\/strong> section and then define the fields as shown in the following illustration.<\/p>\n

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

      \n
    1. In the 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