vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Optional: Click Authentication settings to specify the authentication type to apply to one or more of the starting URLs:



* Choose the starting URL.
* Choose the authentication type from the following options:



* Basic authentication
* NTLM authentication
* FORM authentication



* For Basic authentication, provide the following details:

Username
: The username of a user with access to the content that you want to connect to on the website.

Password
: The password that is associated with the user.
* For NTLM authentication, provide the following details:

Username
: The username of a user with access to the content that you want to connect to on the website.

Password
: The password that is associated with the user.

NTLM domain name
: The NTLM domain name that belongs to the user who is authenticating.

NTLM host name
: The hostname of the NTLM server.
* For FORM authentication, provide the following details:



* In Form type, select one of the following options:

Direct
: Click this option if you do not want to fetch the login page.

Indirect
: Click this option if you want to fetch the login page and you want to fill the parameters in the login form.
* Complete the following fields if you choose Direct:

Form action url
: The form action URL that is required to submit the form.

Form method
: Specify GET.
* Complete the following fields if you choose Indirect:

Form login url
: This field is required if you select the Indirect form type.

Form name
: This field is required if you select the Indirect form type.

Form method
: Specify POST.
* In the Form parameters section, list of the key-value pairs of form parameters.

Complete the Key and Value fields, and then click + to add one or more form parameters.





10. Optional: If you are using a proxy server to access the data source server, then in the Proxy settings section, set the Enable proxy settings switch to On. Add values to the following fields:

Username
If you use a security group to protect your virtual servers, you need to allow SSH traffic. For more information, see [Creating security groups and rules](https://cloud.ibm.com/docs/security-groups?topic=security-groups-creating-security-groups).







 Why can't I access KVM through a browser? 

If you are unable to connect to the KVM console, review the following troubleshooting tips for help. For more information about accessing the KVM, see [Accessing the KVM console for virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-access-kvm-console).



* [Browser needs updating](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-troubleshooting-virtual-serverupdate-browser)
* You haven’t [established a VPN connection](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-troubleshooting-virtual-servervpn-connection)
* Your [credentials are invalid](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-troubleshooting-virtual-servercheck-credentials)





 Browser needs updating 

Make sure that you're using a supported browser. For more information about IBM Cloud®-supported browsers, see [Browsers](https://cloud.ibm.com/docs/overview?topic=overview-prereqs-platformbrowsers-platform).

The KVM Console opens in a new browser tab or window. If the KVM Console doesn't open, check the browser for any blocked new windows.

If you can't access KVM through your browser, you might need to update your browser. Update your browser and try to access KVM.





 A VPN connection isn't established 

Make sure that a connection is established by using the VPN. If a connection isn't established, a warning displays that a VPN connection is required.
For more information, see the [deprecation details](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecationdep_details).

When you run your app in IBM Cloud® with the express framework, the following changes need to be made to enforce HTTPS instead of HTTP on all pages in your app.

var express = require("express");
var app = express();

app.enable('trust proxy');

app.use (function (req, res, next) {
if (req.secure || process.env.BLUEMIX_REGION === undefined) {
next();
} else {
console.log('redirecting to https');
res.redirect('https://' + req.headers.host + req.url);
}
});

Contribute in GitHub

Open doc issue

Edit topic







Feedback

Focus sentinel

 Give us your feedback 

Tell us about your experience0/1500



Don't include any sensitive or personal information.

How satisfied are you with your experience?

How satisfied are you with your experience?

1

2

3

4

5

info icon

Your feedback is carefully reviewed, but you won't be contacted in response. Need help? Try searching the docs or chatting with the Virtual Assistant in console.

Cancel

Submit

Focus sentinel Cookie Preferences

Your privacy choices

Your privacy choices

!
[Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) ![Yes](https://cloud.ibm.com/docs-content/v1/content/ca9232b3702768f24bb897f48f10778fcda28718/watson-assistant/images/checkmark-icon.svg) 





* The way in which options are presented varies depending on the channel integration. The preference field is supported when possible, but not all channels support drop-down lists or buttons.







 Fields 



 Name Type Description Required? 

 response_type string option Y 
 title string The title to show before the options. Y 
 description string The text of the description that accompanies the options. N
* [Why are my console actions failing in my Chrome browser Version 77.0.3865.90 (Official Build) (64-bit)?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-chrome-v77)
* [When I hover over my node, the status is Status unavailable, what does this mean?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-status-unavailable)
* [When I hover over my node, the status is Status undetectable, what does this mean?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-status-undetectable)
* [Why am I getting the error Unable to get system channel when I open my ordering service?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-troubleshoot-ordering-service)
* [Why did my smart contract installation, instantiation or upgrade fail?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-console-smart-contracts-troubleshoot-entry1)
* [Why is my smart contract fail to install with an error on my peer?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-sc-install)
* [Why is my Node.js smart contract fail to endorse?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-nodejs-endorsement)
(OPTIONAL) To avoid security warnings when accessing content through a web browser, you might want to install "Intermediate CA" certificates. These allow your Citrix Netscaler VPX to share information with connecting clients.

To obtain these intermediate certificates for RapidSSL, visit the following link:

[RapidSSL Intermediate and Root CA Certificates](https://knowledge.digicert.com/generalinformation/INFO1548.htmllinks)

To install and link the certificates, follow the instructions in this [Citrix article](https://support.citrix.com/article/CTX114146).

> show ssl certlink
1) Cert Name: hsmclient7ns CA Cert Name: ICARSSL
Done
If the external service does not require a token, specify any string you want. You cannot leave this field empty.

If you want to see the secret as you enter it, click on the Show password icon ![view icon](https://cloud.ibm.com/docs-content/v1/content/icons/view.svg) before you start typing. After you save the secret, the string is replaced by asterisks and can't be viewed again.
7. In the Timeout field, specify the length of time (in seconds) you want the assistant to wait for a response from the webhook before returning an error. The timeout duration cannot be shorter than 1 second or longer than 30 seconds.
8. In the Headers section, add any headers that you want to pass to the service one at a time by clicking Add header.

For example, if the external application that you call returns a response, it might be able to send a response in multiple different formats. The webhook requires that the response is formatted in JSON. The following table illustrates how to add a header that indicates that you want the resulting value to be returned in JSON format.



Header example

 Header name Header value 

 Content-Type application/json 



The service automatically sends an Authorization header with a JWT; you do not need to add one. If you want to handle authorization yourself, add your own authorization header and it will be used instead.

After you save the header value, the string is replaced by asterisks and can't be viewed again.



Your webhook details are saved automatically.





 Testing the webhook 

Do extensive testing of your webhook before you enable it for an assistant that is being used in a production environment.

Your assistant must have a skill added to it before your webhook can do anything useful. The webhook is triggered only when a message has been processed by your skill, and a response is ready to be returned.

If you enable the setting that returns an error when the webhook call fails, the processing of the assistant is halted entirely if the webhook encounters any issues.
PUT /v1/{crn}/zones/{domain_id}/setting/browser_check internet-svcs.security.update internet-svcs.browser-check-setting.update 
 Get opportunistic encryption settings. GET /v1/{crn}/zones/{domain_id}/setting/opportunistic_encryption internet-svcs.security.read internet-svcs.opportunistic-encryption-setting.read 
 Update opportunistic encryption settings. PUT /v1/{crn}/zones/{domain_id}/setting/opportunistic_encryption internet-svcs.security.update internet-svcs.opportunistic-encryption-setting.update 
 Get challenge TTL settings. GET /v1/{crn}/zones/{domain_id}/setting/challenge_ttl internet-svcs.security.read internet-svcs.challenge-ttl-setting.read 
 Update challenge TTL settings. PUT /v1/{crn}/zones/{domain_id}/setting/challenge_ttl internet-svcs.security.update internet-svcs.challenge-ttl-setting.update 
 Get always use HTTPS settings. GET /v1/{crn}/zones/{domain_id}/setting/always_use_https internet-svcs.security.read internet-svcs.always-use-https-setting.read 
 Update always use HTTPS settings. PUT /v1/{crn}/zones/{domain_id}/setting/always_use_https internet-svcs.security.update internet-svcs.always-use-https-setting.update 
 Get true client IP header settings. GET /v1/{crn}/zones/{domain_id}/setting/true_client_ip_header internet-svcs.zones.read internet-svcs.true-client-ip-header-setting.read 
 Update true client IP header settings.
When advised to use Web browser, use the Jump machine provisioned in the [IBM Cloud VPC provisioning tutorial](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-vpcvpc-bm-vmware-vpc). This Jump machine has network access to the hosts, the private DNS service and vCenter IP to be provisioned. Use url with FQDN, e.g. https://vcenter.vmware.ibmcloud.local as used in this example.

The used variables e.g. $VMWARE_SUBNET_MGMT, $VMWARE_BMS001 and $VMWARE_DNS_ZONE are defined in the previous steps of this tutorial.





 Step 1: Provision VLAN NIC for vCenter 

In this step, you will provision a VLAN NIC for vCenter into Instance Management Subnet using VLAN 100 as the matching VLAN ID. Use server BMS001 / esx-001 here. When creating the VLAN NIC, allow it to float between the hosts.



NIC Parameters

 NIC Subnet VLAN ID Allow float IP MAC 

 vlan-nic-vcenter $VMWARE_SUBNET_MGMT 100 yes provided by VPC provided by VPC 



While IBM Cloud VPC provides both IP and MAC addresses, you only need to use the IP address here when configuring the vCenter to use a static IP.



1. Create VLAN NIC for vCenter and record its IP address:

VMWARE_VNIC_VCENTER=$(ibmcloud is bm-nicc $VMWARE_BMS001 --subnet $VMWARE_SUBNET_MGMT --interface-type vlan --vlan 100 --allow-interface-to-float true --name vlan-nic-vcenter --output json | jq -r .id)
You can refer to step 2 in [Example to set token authentication](https://cloud.ibm.com/docs/CDN?topic=CDN-working-with-token-authenticationexample-to-set-token-authentication).





 Applying the token 

Attach the completed token to the URL for your target content as a query string parameter, cookie, or request header.

Token authentication generally requires the use of browser cookies to deliver a signed token as a step in the authorization process. This can affect devices and browsers that don't support using cookies, such as Apple Safari and HLS devices.

While users can manually enable cookies on any browser, Safari users must manually enable cookies. If not already done, Safari users must set Preferences > Security > Accept Cookies: Always. After this preference is set, no additional interaction is required and token authorization works as designed.







 Example to set token authentication 

The following example illustrates how to set token authentication. One customer wants to protect resources under the path /private/* of www.cdn-domain.com, and the following steps show you how to set the token authentication.



1. Create the encryption key.

The key is an even number of hex digits for the token key. An entry can be up to 64 characters in length. To ensure that your key is random, it is recommended that you create the key by using the [OpenSSL tool](https://www.openssl.org/).

For example:

openssl rand -hex 32

The output looks like:

87e23a68764b79b4deb46a521ae7a8a49f156460e6461f3b6cc633bf8a548381

You can also generate a second transition encryption key to serve as a backup "trusted shared secret." If the token provided by the user is not valid based on the primary encryption key, the Edge server checks the token using the transition key. This ensures that users are not denied access if you are in the process of rotating the primary key.

This assumes that you transitioned to generating your tokens with the transition key for some period of time before updating the encryption key value.
[Navigate icon](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/images/navigate_to_icon.png) > Dashboard.
2. Click + Add > **Catalog **. The Add Catalog window is displayed.
3. Enter the name of your new Catalog in the Display Name field.
4. Enter the text that you want to form the Catalog segment of the URL, in the Name field.

The Name field can contain only lowercase alphanumeric characters (a-z and 0-9), or a hyphen (-). A hyphen cannot be used as the first or last character in the name.
5. Click Add. Your Catalog is created, and is displayed on your dashboard.
6. To configure the Catalog, click the name of the Catalog, then click Settings > Info, and proceed with the following steps:



1. If the new Catalog is a development Catalog, select Development mode.



If you select the development mode, staging and publishing actions are forced, meaning that if you republish a previously published Product it is overwritten without warning. If conflicts are found, they are automatically resolved by the system. Unpublish actions happen automatically. **

Approval boxes are not displayed for development Catalogs. You cannot enable the approval process for lifecycles.



2. If you want to enable automatic subscription for the Catalog, select Automatic subscription. Enabling automatic subscription makes testing of your APIs easier because a test application is used, with a pre-supplied client ID and client secret, which is automatically subscribed to all the Plans in the Catalog, so you don't have to specify a plan or application when testing.

Automatic subscription is available only for a development Catalog.
3. If the Catalog is the default staging Catalog, select Default. Calls to APIs that are published to the Catalog can use a shorter URL that does not include the Catalog name .

You can only select Default for one Catalog.
4.
For the key, enter __bx_creds. For the value, paste in the service credentials JSON object from the service instance that you created earlier.











 Using the Tone Analyzer package 

To use the actions in this package, run commands in the following format:

ibmcloud fn action invoke tone-analyzer-v3/<action_name> -b -p <param name> <param>

All actions require a version parameter in the format YYYY-MM-DD. When the API is changed in a backwards-incompatible way, a new version date is released.

This package's functions use the current version of Tone Analyzer, 2017-09-21. Try out the tone action.

ibmcloud fn action invoke tone-analyzer-v3/tone -b -p version 2017-09-21 -p text "i hope you're having a wonderful day"
We recommend that you not use - in the load balancer name to avoid issues with Kubernetes clusters.
* I got a 502 error attempting to save an Edge Functions Action, what do I do?

Contact [IBM support](https://cloud.ibm.com/docs/cis?topic=cis-gettinghelp) and provide the script that you were attempting to save.
* How do I find my service instance ID?

To find your service instance ID, copy the CRN on the overview page. For example:

crn:v1:test:public:internet-svcs:global:a/2c38d9a9913332006a27665dab3d26e8:836f33a5-d3e1-4bc6-876a-982a8668b1bb::

The last part of the CRN is your service instance: 836f33a5-d3e1-4bc6-876a-982a8668b1bb.

Alternatively, you can click the row containing the CIS instance on the resource list main page and copy the GUID for the service instance ID.
* Does CIS compress resources?

Yes, CIS applies "gzip" and "brotli" compression to some types of content. CIS also compresses items based on the browser's UserAgent to speed up page loading time.

If you're already using gzip CIS honors your gzip settings as long as you're passing the details in a header from your web server for the files.

CIS only supports the content type "gzip" towards your origin server and can also only deliver content either gzip-compressed, brotli-compressed, or not compressed.

CIS's reverse proxy is also able to convert between compressed formats and uncompressed formats, meaning that it can pull content from a customer's origin server via gzip and serve it to clients uncompressed (or vice versa). This is done independently of caching.

The Accept-Encoding header is not respected and is removed.



Content Delivery Network (CDN)



* How does the CDN edge server retrieve content from the origin server?
{"ClientIP":"2620:1f7:8c5::1f:949e:c04d","ClientRequestHost":"test.logpull.load.com","ClientRequestMethod":"GET","ClientRequestURI":"/assets/bootstrap-modal.js","EdgeEndTimestamp":1545067628046000000,"EdgeResponseBytes":2569,"EdgeResponseStatus":200,"EdgeStartTimestamp":1545067628043000000,"RayID":"48ab1943488ac7a7"}
{"ClientIP":"2620:1f7:8c5::1f:949e:c04d","ClientRequestHost":"test.logpull.load.com","ClientRequestMethod":"GET","ClientRequestURI":"/assets/holder.js","EdgeEndTimestamp":1545067628053000000,"EdgeResponseBytes":4593,"EdgeResponseStatus":200,"EdgeStartTimestamp":1545067628046000000,"RayID":"48ab19434898c7a7"}
{"ClientIP":"2620:1f7:8c5::1f:949e:c04d","ClientRequestHost":"test.logpull.load.com","ClientRequestMethod":"GET","ClientRequestURI":"/assets/old_school.png","EdgeEndTimestamp":1545067627960000000,"EdgeResponseBytes":1466,"EdgeResponseStatus":200,"EdgeStartTimestamp":1545067627952000000,"RayID":"48ab1942bf92c7a7"}
Why do I encounter console pages that don't load? 

A page in the IBM Cloud® console might not load properly, and an error message is displayed.

  What’s happening 

One of the following error messages might be displayed:

> BXNUI0001E: The page wasn't loaded because IBM Cloud didn't detect whether a session exists.

or

> BXNUI0016E: The apps and services weren't retrieved because an IBM Cloud page didn't load.

or

> 500 internal server error

  Why it’s happening 

An issue with the browser is causing a console page to not load. Or, there might be a temporary issue with connectivity.

  How to fix it 

Complete one or more of the following actions, as necessary:



*  Refresh or restart your browser.
*  Log out of the console and log in again.
*  Use the private browsing mode of your browser.
*  Clear the cookies and the cache of the browser.
*  Use a different browser. For the list of supported browsers, see [IBM Cloud prerequisites](https://cloud.ibm.com/docs/overview?topic=overview-prereqs-platform).
*  If the problem persists, go to the [IBM Cloud Status page](https://cloud.ibm.com/status) to check if a service or component has an issue.
For more information, see [TLS protocol overview](https://www.ibm.com/docs/en/sdk-java-technology/8?topic=provider-tls-protocol-overview).
* Must be hosted on a valid HTTPs endpoint that is accessible on the public internet







 Testing your service's broker 

You must validate your broker by running curl commands against the different endpoints that you enable. You need the hosted location of your service broker and the URL and credentials that are associated with your application. To test your broker, use the following methods:



* The sample readme file guidance for curling your OSB endpoints: [https://github.com/IBM/sample-resource-service-brokers/blob/master/README.md](https://github.com/IBM/sample-resource-service-brokers/blob/master/README.md).
* The Open Service Broker Reference App guidance for testing your broker: [Testing the broker](https://github.com/IBM-Cloud/onboarding-osbtesting-the-broker)





 Example curl request 

Use the following example to test your brokers curl response:
* [What is the expected behavior when loading the CNAME or hostname on your browser for the supported protocols?](https://cloud.ibm.com/docs/CDN?topic=CDN-troubleshoot-cdn-loading-cname-hostname)



* [Getting help and support for CDN](https://cloud.ibm.com/docs/CDN?topic=CDN-gettinghelp)



* [Go to product UI](https://cloud.ibm.com/cdn) [About this product](https://www.ibm.com/cloud/cdn)



Expand all | Collapse all

Collapse



1. [IBM Cloud Docs](https://cloud.ibm.com/docs)
2. [Content Delivery Network (CDN)](https://cloud.ibm.com/docs/CDN)
3.



Search in collection

Search in collection





LangSwitcher dropdown

English

Close menu

DeutschEnglish

EspañolFrançaisItaliano日本語한국어Português/Brasil简体中文繁體中文





 Why can't I connect through a curl command or browser using the hostname with HTTPS? * Last updated 2020-01-08 

If your CDN was created using HTTPS with a wildcard certificate, the connection must be made using the CNAME; for example, https://www.exampleCname.cdn.appdomain.cloud. This includes all CDNs created with HTTPS before 18 June 2018. Trying to connect using the hostname results in an error.

Contribute in GitHub

Open doc issue

Edit topic







Feedback

Focus sentinel

 Give us your feedback 

Tell us about your experience0/1500



Don't include any sensitive or personal information.

How satisfied are you with your experience?

How satisfied are you with your experience?

1

2

3

4

5

info icon

Your feedback is carefully reviewed, but you won't be contacted in response. Need help?
serviceInstanceID: 'YOUR_SERVICE_INSTANCE',
cloudPrivateHostURL: 'YOUR_HOST_URL',
onLoad: function(instance) {
instance.updateUserID('L12345');
instance.render();
}
};
setTimeout(function(){
const t=document.createElement('script');
t.src='https://web-chat.global.assistant.dev.watson.appdomain.cloud/versions/' +
(window.watsonAssistantChatOptions.clientVersion || 'latest') +
'/WatsonAssistantChatEntry.js';
document.head.appendChild(t);
});
</script>
Show more