vania-janet/multiturn-rag-retrieval-data huggingface dataset:
When identifying the credentials, it might be useful to consult the [Salesforce developer documentation](https://developer.salesforce.com/docs/).

Other items to note when you crawl Salesforce:



* Knowledge Articles are only crawled if their version is published and their languages is en-us.
* When you use the API, you must have a list of Salesforce objects that you want to crawl. Use the Discovery tooling to browse and select which content to crawl.







 SharePoint Online 

When connecting to a Microsoft SharePoint Online source, ensure that the instance that you plan to connect to is an Enterprise (E1) plan or higher.

Except for site_collection_path, the following fields are required to connect to a SharePoint Online source. If you do not know what to enter in these fields, contact your SharePoint administrator, or consult the [Microsoft SharePoint developer documentation](https://docs.microsoft.com/en-us/sharepoint/dev/):



* username - The username to connect to the SharePoint Online SiteCollection that you want to crawl. This user must have access to all sites and lists that the user wants to crawl and index. Your username input must be a default Azure Active Directory (Azure AD) account, which is formatted as follows: <username>@<domain>.onmicrosoft.com. If you do not have an Azure AD username, contact your SharePoint site administrator.
* password - The password to connect to the SharePoint Online SiteCollection that you want to crawl. This value is never returned and is only used when creating or modifying credentials.
* organization_url - The organization_url of the source that you want to crawl. When you enter this input, only enter the domain name of the URL, for example https://<company>.<domain>.com/. If you enter a URL that extends beyond the domain name, or .com/, the input is invalid. Replace <company> and <domain> with the corresponding parts of the organization URL that you want to crawl.
* site_collection_path Optional: - The site_collection_path to the source that you want to crawl.
Troubleshooting API Connect 

Here are the answers to common troubleshooting questions about using IBM® API Connect.



 Username and password required when adding the API Connect service 

After you add the service to your IBM Cloud Dashboard, you are prompted for a username and password when you try to open it.

 What’s happening 

Instead of accessing the IBM Cloud service directly when you open a new API Connect, it requires you to log in to the API Manager.

 Why it’s happening 

Your browser is set to block cookies, or the level is set to a more restricted level than API Connect requires.

 How to fix it 

Enable or increase the permission level of cookies in your browser settings until it opens the IBM Cloud service.





 Incorrect permissions after logging in to API Connect 

You log in to API Connect successfully but have no permissions.

 What’s happening 

You are unable to complete tasks that you normally have permissions to execute.

 Why it’s happening 

Possible issue with the server, which might be corrected with a fresh login.

 How to fix it 

Take these steps:



1. Log out.
2. Wait several minutes to ensure the logout operation completes.
3. Log in again and try to complete the tasks.



If the permissons issue still persists, contact [API Connect Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).





 Unable to install the developer toolkit 

After you provision the API Connect service, you try to install the developer toolkit and the installation fails.

 What’s happening 

The following errors are displayed during the developer toolkit installation:

npm ERR! Error: EACCES, mkdir '/usr/local/lib/node_modules/apiconnect'
...
npm ERR! Please try running this command again as root/Administrator
...

 Why it’s happening 

You don't have the required rights to create files or directories.

 How to fix it 

Change the rights for the specified directories, or run the command using sudo.
The feed action can also accept any other parameters that it needs to manage the feed. For example, the IBM Cloudant changes feed action expects to receive parameters that include dbname and username.

When you create a trigger from the CLI with the --feed parameter, the feed action is automatically invoked with the appropriate parameters.

For example, create a mycloudant binding for the cloudant package with a username and password as bound parameters. When the user issues the following command from the CLI:

ibmcloud fn trigger create my_cloudant_trigger --feed mycloudant/changes -p dbName myTable

Or using the trigger feed parameters:

ibmcloud fn trigger create my_cloudant_trigger --feed mycloudant/changes --feed-param dbName myTable

Then, invoke the trigger with something equivalent to the following command:

ibmcloud fn action invoke mycloudant/changes -p lifecycleEvent CREATE -p triggerName T -p authKey <userAuthKey> -p password <password value from mycloudant binding> -p username <username value from mycloudant binding> -p dbName mytype

The feed action that is named changes takes these parameters and is expected to perform whatever action is necessary to set up a stream of events from IBM Cloudant. The feed action occurs by using the appropriate configuration, which is directed to the trigger.

For the IBM Cloudant changes feed, the action talks directly to an IBM Cloudant trigger service that is implemented with a connection-based architecture.

A similar feed action protocol occurs for ibmcloud fn trigger delete, ibmcloud fn trigger update, and ibmcloud fn trigger get.





 Implementing feeds with hooks 

Set up a feed by using a hook when an event producer supports a webhook-callback facility.

With this method, you are not required to stand up any persistent service outside of Cloud Functions. All feed management happens naturally though stateless Cloud Functions feed actions, which negotiate directly with a third-party webhook API.
Connecting an external application 

Your applications and drivers use connection strings to make a connection to IBM Cloud® Databases for Redis. The service provides connection strings specifically for drivers and applications. Connection strings are displayed in the Endpoints panel of your deployment's Overview, and can also be retrieved from the [cloud databases CLI plugin](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployment-connections), and the [API](https://cloud.ibm.com/apidocs/cloud-databases-apidiscover-connection-information-for-a-deployment-f-e81026).



 Connection Strings for Applications 

The information a driver needs to make a connection to your deployment is in the "redis" section of your connection strings. The table contains a breakdown for reference.



Table 1. redis/URI connection information

 Field Name Index Description 

 Type Type of connection - for Redis, it is "URI" 
 Scheme Scheme for a URI - for Redis, it is "rediss" 
 Path Path for a URI - for Redis, it is the database number 
 Authentication Username The username that you use to connect. 
 Authentication Password A password for the user - might be shown as $PASSWORD 
 Authentication Method How authentication takes place; "direct" authentication is handled by the driver. 
 Hosts 0... A hostname and port to connect to 
 Composed 0... A URI combining Scheme, Authentication, Host, and Path 
 Certificate Name The allocated name for the self-signed certificate for database deployment 
 Certificate Base64 A base64 encoded version of the certificate. 





* 0... indicates that there might be one or more of these entries in an array.



Redis drivers are often able to make a connection to your deployment when given the URI-formatted connection string found in the "composed" field of the connection information. For example, if you set the connection string in the environment variable REDIS_URL
Connecting an external application 

Your applications and drivers use connection strings to make a connection to IBM Cloud® Databases for Elasticsearch. Each deployment has connection strings specifically for drivers and applications. Connection strings are displayed in the_Endpoints_panel of your deployment's_Overview_, and can also be retrieved from the [cloud databases CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployment-connections), and the [API](https://cloud.ibm.com/apidocs/cloud-databases-apidiscover-connection-information-for-a-deployment-f-e81026).

The connection strings can be used by any of the credentials you have created on your deployment. While you can use the admin user for all of your connections and applications, it might be better to create users specifically for your applications to connect with. Documentation on creating users is on the [Creating Users and Getting Connection Strings](https://cloud.ibm.com/docs/databases-for-elasticsearch?topic=databases-for-elasticsearch-connection-strings) page.



 Connecting with a language's driver 

All the information a driver needs to make a connection to your deployment is in the "https" section of your connection strings. The table contains a breakdown for reference.



Table 1. https/URI connection information

 Field Name Index Description 

 Type Type of connection - for Elasticsearch, it is "uri" 
 Scheme Scheme for a URI - for Elasticsearch, it is "https" 
 Path Path for a uri 
 Authentication Username The username that you use to connect. 
 Authentication Password A password for the user - might be shown as $PASSWORD 
 Authentication Method How authentication takes place; "direct" authentication is handled by the driver. 
 Hosts 0... A hostname and port to connect to 
 Composed 0... A URI combining Scheme, Authentication, Host, and Path 
 Certificate Name The allocated name for the self-signed certificate for database deployment 
 Certificate Base64 A base64 encoded version of the certificate.
* [MQRC_MAX_CONNS_LIMIT_REACHED (2025) when attempting to connect to a queue manager](https://cloud.ibm.com/docs/mqcloud?topic=mqcloud-mqoc_common_problemsmqoc_client_conn_limit)
* [Messages cannot be put to a queue whose name does not start with 'DEV.'](https://cloud.ibm.com/docs/mqcloud?topic=mqcloud-mqoc_common_problemsmqoc_auth_record)





 Client application receives a "not authorized" response when attempting to connect to a queue manager even though a valid userid and password is supplied. 

While attempting to connect a client application to your IBM MQ on Cloud queue manager you receive a return code indicating that the user was not authenticated successfully, such as one or more of the following;



* In MQ Explorer, Access not permitted. You are not authorised to perform this operation (AMQ4036)
* In a JMS or Java application MQRC_NOT_AUTHORIZED (2035)
* AMQ9791E: The client application did not supply a user ID and password.





 First Explanation 

The default configuration of a IBM MQ on Cloud queue manager specifies that any application connecting to the queue manager must supply valid user credentials. Users and applications can have credentials created by following the instructions in the [Users and Applications document page](https://cloud.ibm.com/docs/services/mqcloud?topic=mqcloud-mqoc_users_and_apps).

IBM MQ client applications have two different methods of supplying credentials to a queue manager that is controlled by a switch called compatibility mode. You must ensure that when the application is connecting it is has compatibility mode disabled, otherwise only the first 8 characters of the password (long API key) is transmitted to the queue manager, and so the authentication check fails.

Client applications connecting using IBM MQ client libraries below version 8.0.0.0 are unable to supply long user credentials to the queue manager using this newer method and so will be unable to connect.





 First Solution
* Is the vSRX firewall blocking SSH access to the private IP? The firewall rules must allow SSH access to the private 10.0.0.0/8 subnet. For more information, see [IBM Cloud IP ranges](https://cloud.ibm.com/docs/hardware-firewall-shared?topic=hardware-firewall-shared-ibm-cloud-ip-rangesservice-network-on-back-end-private-network-) for the service network.
* Is the root password listed on the Gateway Appliance Details page the correct password for the root user? If not, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/af86f2de476b09efc2fa731457e7b3e58571f062/icons/edit-tagging.svg) next to the root password and change the password to match the actual root password for the vSRX.
* Is the root user account disabled for SSH access to the vSRX?







 Correcting error 1124 

vSRX 18.4R1-S1 introduced an incompatibility documented in this [Juniper problem report](https://prsearch.juniper.net/InfoCenter/index?page=prcontent&id=PR1407295). You require a Juniper account to access this report.

If a redundant Ethernet (reth) interface includes vlan-tagging (which is the default), then the interface must also include the vlan-id tag. In 18.4R1-S1, it was possible to commit a configuration without the vlan-id tag. Newer versions, such as 19.4R2-S3, do not allow this configuration.

An example configuration without the vlan-id:

set interfaces reth2 vlan-tagging
set interfaces reth2 mtu 9000
set interfaces reth2 redundant-ether-options redundancy-group 1
set interfaces reth2 unit 2058 family inet address xx.xx.xxx.1/26
commit check
Connecting an external application 

Your applications and drivers use connection strings to make a connection to IBM Cloud® Messages for RabbitMQ. Your deployment has connection strings specifically for drivers, clients, and applications. Connection strings are displayed in the Endpoints panel of your deployment's Overview, and can also be retrieved from the [cloud databases CLI plug-in](https://cloud.ibm.com/docs/databases-cli-plugin?topic=databases-cli-plugin-cdb-referencedeployment-connections), and the [API](https://cloud.ibm.com/apidocs/cloud-databases-apidiscover-connection-information-for-a-deployment-f-e81026).

The connection strings can be used by any of the credentials you created on your deployment. While you can use the admin user for all of your connections and applications, it might be better to create users specifically for your applications to connect with. Documentation on creating users is on the [Creating Users and Getting Connection Strings](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-connection-strings) page.



 Connecting with a language's driver 

The information a driver needs to make a connection to your deployment is in the amqps section of your connection strings. The table contains a breakdown for reference.



Table 1. RabbitMQ/uri connection information

 Field Name Index Description 

 Type Type of connection - for RabbitMQ, it is uri 
 Scheme Scheme for a URI - for RabbitMQ, it is amqps 
 Path Path for a uri 
 Authentication Username The username that you use to connect. 
 Authentication Password A password for the user - might be shown as $PASSWORD 
 Authentication Method How authentication takes place; "direct" authentication is handled by the driver. 
 Hosts 0... A hostname and port to connect to 
 Composed 0... A URI combining Scheme, Authentication, Host, and Path 
 Certificate Name The allocated name for the self-signed certificate for database deployment 
 Certificate Base64 A base64 encoded version of the certificate. 





* 0...
[Edit icon](https://cloud.ibm.com/icons/icon_write.svg) to enter a new VPN password.
4. Click Apply.



* What can I do if I forget my password?

If you don't remember your password for your IBMid and can't log in to IBM Cloud, you can reset your password by using our [automated system](https://www.ibm.com/account/reg/us-en/reset-password).
* Can I remove my personal data from IBM Cloud?

To understand how IBM handles your personal information, see the [IBM Privacy Statement](https://www.ibm.com/privacy). In the Your Rights section, review the information about what you can request to remove. Click the link in the section to submit a request to remove your personal information.
* Why is my account deactivated?

Your account might be deactivated for the following reasons:



* For trial accounts, the trial period ended. To reactivate your account, log in to your account and upgrade it to a Pay-As-You-Go account.
* An authorized user closed the account.
* An account has past due invoices and several contact attempts have been made by IBM Cloud Support to make payment arrangements.
* At the discretion of IBM, accounts that violate the acceptable usage behavior of the IBM Cloud services can be disabled without notice. Some services can be restored if users correct their usage behaviors after they're notified of the offensive action. For more information, see [Acceptable Internet use policy for IBM services](https://www.ibm.com/services/us/imc/html/aup1.html).



If you believe that your account was deactivated in error, contact support by calling 1-866-325-0045 and selecting the third option.
* What are my options for contacting IBM Cloud Support?

From the IBM Cloud console menu bar, click the Help icon ![Help icon](https://cloud.ibm.com/icons/help.svg) > Support center. The options that are available to you depend on your support plan.
You can manage standard keys by following steps in [Manage your keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-get-startedmanage-keys).





 Data encryption keys 

Data encryption keys (DEKs) are cryptographic keys that you use for data encryption. They are provided by user-owned applications and are used to encrypt data stored in applications. Root keys that you manage in Hyper Protect Crypto Services serve as wrapping keys to protect DEKs. To learn more, see [Introduction to envelope encryption](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-envelope-encryption).





 Envelope encryption 

Envelope encryption is the practice of encrypting data with a DEK and then encrypting the DEK with a root key that you can fully manage. To learn more, see [Introduction to envelope encryption](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-envelope-encryption).







 Cloud hardware security module 

This section covers concepts that are related to Hyper Protect Crypto Services [Cloud Hardware Security Module (HSM) feature](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-overviewcloud-hsm). The list starts with the most fundamental concepts.



 Hardware security module 

A hardware security module (HSM) is a physical device that safeguards and manages digital keys for strong authentication and provides crypto-processing. HSMs of IBM Cloud Hyper Protect Crypto Services are FIPS 140-2 Level 4 certified, which is the highest level of security for cryptographic hardware. At this security level, the physical security mechanisms provide a complete envelope of protection around the cryptographic module with the intent of detecting and responding to all unauthorized attempts at physical access.





 Crypto units 

A crypto unit is a single unit that represents an HSM and the corresponding software stack that is dedicated to the HSM for cryptography. In Hyper Protect Crypto Services, the following types of crypto unit are available:



* Operational crypto unit
You can manage standard keys by following steps in [Manage your keys](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-get-startedmanage-keys).





 Data encryption keys 

Data encryption keys (DEKs) are cryptographic keys that you use for data encryption. They are provided by user-owned applications and are used to encrypt data stored in applications. Root keys that you manage in Hyper Protect Crypto Services serve as wrapping keys to protect DEKs. To learn more, see [Introduction to envelope encryption](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-envelope-encryption).





 Envelope encryption 

Envelope encryption is the practice of encrypting data with a DEK and then encrypting the DEK with a root key that you can fully manage. To learn more, see [Introduction to envelope encryption](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-envelope-encryption).







 Cloud hardware security module 

This section covers concepts that are related to Hyper Protect Crypto Services [Cloud Hardware Security Module (HSM) feature](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-uko-overviewuko-cloud-hsm). The list starts with the most fundamental concepts.



 Hardware security module 

A hardware security module (HSM) is a physical device that safeguards and manages digital keys for strong authentication and provides crypto-processing. HSMs of IBM Cloud Hyper Protect Crypto Services are FIPS 140-2 Level 4 certified, which is the highest level of security for cryptographic hardware. At this security level, the physical security mechanisms provide a complete envelope of protection around the cryptographic module with the intent of detecting and responding to all unauthorized attempts at physical access.





 Crypto units 

A crypto unit is a single unit that represents an HSM and the corresponding software stack that is dedicated to the HSM for cryptography. In Hyper Protect Crypto Services, the following types of crypto unit are available:



* Operational crypto unit
Why can't I authenticate to my Watson service? 

You try to authenticate to a Watson service but receive an error message.

 What’s happening 

When you send your credentials through a Watson API, you receive a 401 HTTP status code.

For example,

{
"trace":"ec29c5a9-9f99-46a4-9cc0-81a0d4031f84",
"error":"Unauthorized",
"more_info":"https://cloud.ibm.com/docs/watson?topic=watson-authorization-error",
"code":401
}

 Why it’s happening 

A 401 HTTP status code indicates that you are not authenticated. 401 is similar to [403](https://cloud.ibm.com/docs/watson?topic=watson-forbidden-error), but refers only to authentication, not permissions or authorization.

Common causes include these situations:



* The access token is expired.
* The password or API key values include the placeholder brackets ({, }).
* The instance uses username and password authentication.
* The SDK authentication initialization is the wrong method.



 How to fix it 

Validate your credentials or try to authenticate with a different command.



* Check your API key and endpoint URL against the service instance by clicking the name of the service instance in the [Resource list](https://cloud.ibm.com/resources?groups=resource-instance) and verifying the credentials.
* If you are using an authorization or service ID to grant access, make sure that you use an endpoint URL that includes the service instance ID. You can find the instance ID by clicking the name of the service instance in the [Resource list](https://cloud.ibm.com/resources?groups=resource-instance) and looking at the credentials URL.
* If you are authenticating through an SDK or other wrapper, call the method with a curl command. Using curl can help isolate whether you have an authentication issue.