Authentication
As all AI/LLM functionality is provided by external services utilising a Bring Your Own Model (BYOM) approach, authentication is required to access these services. The authentication methods vary depending on the service being used. The below covers authentication details for model providers that are available out of the box.
Clients are expected to manage licensing and provide their own credentials to use the LLM functionality; this may result in additional charges based on the chosen model.
OpenAI
The OpenAPI models utilise a named credential and an external credential to authenticate with the OpenAI API.
The named credential, called OpenAI (seven20__OpenAI), has the following headers which must be provided:
| Header | Description |
|---|---|
| OpenAI-Organization | Organisation Id as provided by OpenAI |
| OpenAI-Project | Project Id as defined in OpenAI. It is best practice to use a dedicated project for Seven20 |
The external credential is linked to the named credential and called OpenAI (seven20__OpenAI) - edit the Principal and add the following authentication parameters:
| Parameter | Description |
|---|---|
| API Key | The API key created within OpenAI. It is best practice to use a dedicated key for Seven20 |
Azure OpenAI
The Azure OpenAI models utilise a named credential and an external credential to authenticate with the Azure OpenAI API.
The named credential, called Azure OpenAI (seven20__AzureOpenAI), needs the URL to be updated to match that of the client's Azure account.
For example, edit this https://{ACCOUNT}.openai.azure.com/ to this https://seven20.openai.azure.com/
The external credential is linked to the named credential and called Azure OpenAI (seven20__AzureOpenAI) - edit the Principal and add the following authentication parameters:
| Parameter | Description |
|---|---|
| API Key | The API key created within Azure OpenAI. It can be either API Key 1 or 2, depending on credential lifecycle |