Skip to main content
Back to App Settings The Platform’s Enterprise Integration Framework supports multiple authentication models configurable at a task level for each assistant, enabling both authenticated and unauthenticated tasks in the same configuration. Developers can build custom authentication profiles for AI Agents by defining subdomains through tenancy URLs, adding new fields through IDP form fields, and more. They can also test and validate the authorization definition before proceeding. The Platform passes user identity information and authentication tokens to the context as the web and mobile SDK initializes, so your AI Agent can leverage existing authentication and authorization settings for end users.

Supported Authentication Models

The Platform lets you enable one authentication profile across all AI Agents and tasks, or create custom profiles for each assistant and task. Configure authentication for your assistant to access third-party web services using the following authorization types.

Basic Auth

A standard protocol to collect username and password information. Kore.ai uses SSL encryption in combination with basic authentication to help secure end-user information. For more information, see Setting Up Authorization using Basic Auth.

OAuth v2 password grant type

Define a custom authorization type for non-standard web service authorization types. For more information, see Setting Up Authorization using OAuth v2 password grant.

OAuth v2 client credentials

Configure authorization using client credentials. Learn more.

OAuth v2

The newest version of the OAuth protocol focusing on specific authorization flows for web applications and web services. For more information, see Setting Up Authorization using OAuth v2.

OAuth v1

Enables web applications or web services to access protected resources using an API without end-users disclosing their login credentials to Kore.ai. For more information, see Setting Up Authorization using OAuth v1.

API Key

Identification and authorization token generated or provided by a web application or web service to identify the incoming application request, and in some cases, also provides authentication for secure access. For more information, see Setting Up Authorization using an API Key.

Kerberos SPNEGO

Enables enterprises to use Kerberos SPNEGO authentication flow to connect securely with their internal applications using this security protocol. For more information, see the Setting Up Kerberos SPNEGO authorization profile article.

Authorization Options

Each authorization you add to your assistant comes with several options accessible by selecting an authorization profile under App Settings > Dev Tools > Authorization Profiles.
  • Test – Click the Test button corresponding to an authorization to test the authorization profile and verify that the assistant establishes a connection to the linked app. Test steps differ depending on the authorization model. See the documentation for each model for details.
  • Edit – Click the gear icon corresponding to an authorization, then select Edit to open the editing dialog and modify the authorization details.
  • Delete – Click the gear icon corresponding to an authorization, then select Delete. Confirm your choice to delete the authorization profile.
Warning: Deleted authorization profiles can’t be restored. Please proceed with caution.
Authorization Options