vania-janet/multiturn-rag-retrieval-data huggingface dataset:
: When you create a binding between your Code Engine workload and a service instance, the service binding is active as long as the Code Engine workload and the service instance is active, or you haven't completed an unbind operation to remove the service binding. If the service instance is deleted, you'll need to manually delete the service binding. When you unbind (or remove) a service binding, you are deleting the association of the app or job with the service access secret such that the app or job no longer has access to previously bound IBM Cloud service.





 Accessing a bound service instance from a Code Engine workload 

Code Engine provides environment variables for accessing service instances that are bound to your Code Engine workload with both the [CE_SERVICES](https://cloud.ibm.com/docs/codeengine?topic=codeengine-service-bindingce-services) and [PREFIX](https://cloud.ibm.com/docs/codeengine?topic=codeengine-service-bindingprefix-method) methods.



* The CE_SERVICES environment variable is a single environment variable that contains all service binding information as a JSON object.
* Code Engine also creates multiple environment variables for your service binding, which are based on the variables in the service credential for your service instance. To distinguish these multiple environment variables for your service binding, you can use a PREFIX such that these environment variables use the same prefix. If you do not specify a custom prefix, Code Engine automatically generates a prefix.



If your application, job, or function wants to talk to a bound service by using private networking and the service has both private and direct endpoints (such as IBM Cloud Object Storage), then the direct endpoints must be used.



 CE_SERVICES environment variable 

The CE_SERVICES environment variable contains information that you can use to interact with a service instance. This environment variable points to a JSON object that contains key value pairs. These key value pairs represent each type of service that is bound to your application. The key is the name of the service type, such as cloud-object-storage, and the value is an array of credentials for bound service instances of that type.

The following example illustrates a CE_SERVICES variable:

{
A service key is a unique code that is passed in an API request to identify the calling application or user. The service key is specific to a logging instance. For more information on how to generate a service key, see [Managing service keys](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_keys).

For example, to get information on an service key that is available in an instance in US South, you can run the following request:

curl https://api.us-south.logging.cloud.ibm.com/v1/config/keys/123456789 -H "content-type: application/json" -H "servicekey: xxxxxxxxx"





 Create a key 

curl -X POST https://API_ENDPOINT/v1/config/keys?type="service"
-H 'content-type: application/json' -H 'servicekey: SERVICE_KEY' -d '{"name": "KEY_NAME"}'

Where:

API_ENDPOINT
: Depending on [your account settings](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview), you can use public or private endpoints to manage categories programmatically. For information about endpoints per region, see [API endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_api).

SERVICE_KEY
: Service key value. A service key is a unique code that is passed in an API request to identify the calling application or user. The service key is specific to a logging instance. For more information on how to generate a service key, see [Managing service keys](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-service_keys).

KEY_NAME
: Name that you want to give the key. The maximum size of a name is 30 characters.





 Change the name of a key
Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 







 Toolchain 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use toolchain for the service name.

Platform roles

Service roles

Actions



Table 152. Platform roles - Toolchain
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 Transit Gateway 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use transit for the service name.

Service roles

Actions



Table 153. Service roles - Transit Gateway
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the service role name and the column headers identify the specific information available about each role.

 Role Description 

 Manager As a manager, you have permissions beyond the writer role to complete privileged actions as defined by the service. In addition, you can create and edit service-specific resources. 







 Transit Gateway 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use transit.gateway for the service name.

Platform roles

Actions



Table 154. Platform roles - Transit Gateway
A service ID can be assigned access policies and used to enable an application that is deployed to a cloud environment access to cloud services.





 session 

The period of time after an app is started on a mobile device and the quality assurance product is notified to begin collecting app behavior, issues, and problems.





 signature key 

An encryption key that is used by the crypto unit administrator to sign commands that are issued to the crypto unit.





 signCert 

A certificate that any entity, such as an organization or admin, attaches to their proposals or proposal responses. These signCerts are unique to an entity and are checked by the ordering service to make sure they match the signCert on file for that entity.





 single sign-on (SSO) 

An authentication process in which a user can access more than one system or application by entering a single user ID and password.





 single-campus multizone region (single-campus MZR) 

A region that consists of multiple zones that are hosted on data centers that are located within a single building or campus. Dependencies such as power, cooling, networking, and physical security might overlap but are not identical between any two zones to increase fault tolerance. See also [zone](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2070723).





 single-campus MZR 

See [single-campus multizone region](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx10127487).





 single-page application (SPA) 

An application that works inside a browser and does not require page reloading during use.





 smart contract 

A set of business terms that are embedded into a blockchain and executed with transactions. A smart contract can also include a digital representation of a set of business rules and defines conditions under which transfers occur. A smart contract is implemented using chaincode.





 SoE 

See [system of engagement](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx6528306).





 software as a service (SaaS)
Writer As a writer, you have permissions beyond the reader role, including creating and editing service-specific resources. 







 Hyper Protect DBaaS for PostgreSQL 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use hyperp-dbaas-postgresql for the service name.

Service roles

Actions



Table 70. Service roles - Hyper Protect DBaaS for PostgreSQL
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the service role name and the column headers identify the specific information available about each role.

 Role Description 

 Manager As a manager, you have permissions beyond the writer role to complete privileged actions as defined by the service. In addition, you can create and edit service-specific resources. 
 Reader As a reader, you can perform read-only actions within a service such as viewing service-specific resources. 
 Writer As a writer, you have permissions beyond the reader role, including creating and editing service-specific resources. 







 IAM Access Management 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use iam-access-management for the service name.

Platform roles

Actions



Table 71. Platform roles - IAM Access Management
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Viewer As a viewer, you can view service instances, but you can't modify them. 







 Role Management 

Review the available platform and service roles and the actions mapped to each to help you assign access.
Add a line in the Authentication section of the file that says PermitRootLogin yes. This line might exist and be commented out with a "#". In this example, remove the "#".



LoginGraceTime 2m

PermitRootLogin yes

StrictModes yes

MaxAuthTries 6

MaxSessions 10

Save the updated /etc/ssh/sshd_config file.



4. Restart sshd service on Ubuntu or Debian Linux by using the following command:

sudo systemctl restart ssh.service

RHEL and CentOS Linux users, run the following command to restart sshd service:

sudo systemctl restart sshd.service







 Port not configured for SSH 



* Check that the port number configured for ssh in the /etc/ssh/sshd_config file.
* Check the port number that is configured for SSH in the /etc/ssh/sshd_config file. By default, SSH is configured with port 22. However, for security reasons, your administrator might change the port.







 Firewall is blocking SSH traffic 

SSH port traffic might be blocked by your firewall. For more information, see [Allowing SSH and pinging to a public subnet](https://cloud.ibm.com/docs/vsrx?topic=vsrx-allowing-ssh-and-pinging-to-a-public-subnet).







 Why can't I access IPMI IP through a browser? 



* Try to access the IPMI IP through different browser.
* Update your browser and or Java to access IPMI IP.
* If you still have problems, contact [support](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-gettinghelp).







 Why isn't RDP working? 

If you can access your server, but RDP isn't working, it might be caused by one of the following reasons.
* A service access secret cannot be reused in a service binding for the same app or job. However, you can reuse the same service access secret in a different app or job. Because a service access secret is associated with a specific IBM Cloud service instance, you can reuse only the service access secret in a different app or job, if you are binding to the same service instance.



Let's create a service binding to bind a service instance to a job that uses an existing service access secret. For example, create a service binding for the myjob job and choose an existing service access secret for a specific service instance.



1. After your project is in Active status, click the name of your project on the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects).
2. From the Overview page, click Service bindings.
3. From the Service bindings page, click Create to create the binding.
4. Select the IBM service instance that you want to bind to your Code Engine app or job.
5. Select the Code Engine app or job that you want to bind to the service instance.
6. You can reuse an existing credential for the service access secret for a service binding to a specific IBM Cloud service instance with a different app or job. For this case, select Existing secret. Notice that any previously defined service credential for your specific service instance is listed, which is not associated with the app or job that you selected. Complete the following steps.



1. Review the list of existing secrets and select the secret that you want to use with this service binding.
2. (optional) Specify a custom prefix for the service binding. If you do not specify a custom prefix, Code Engine automatically generates a prefix. The prefix is used to distinguish environment variables that are created for this service binding.



7. Click Add to create the service binding.
8. Now that your service binding to your app or job is created from the console, you can view a list of all defined service bindings between service instances and Code Engine apps and jobs from the Service bindings page.
Why isn't the service route for my VPN gateway correct? 

For a policy-based VPN gateway, service routes are propagated to routing tables that have VPN gateway selected for the Accepts routes from attribute. These routes have names prefixed with ibm-vpn-gateway-.

  What’s happening 

In this rare instance, you might find that these service routes are not correct. For example, the Next hop is not same as the private IP of your active gateway member. In this case, traffic is broken even if the VPN connection is Active.

  Why it’s happening 

The VPN gateway service keeps monitoring the health of each VPN gateway. When a fault is detected, the service tries to recover the VPN gateway automatically. The recovery process might fail and cause inaccurate routes to remain.

  How to fix it 

Follow these steps to fix the service routes:



1.  From your browser, open the [IBM Cloud console](https://cloud.ibm.com/login) and log in to your account.
2.  Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) on the upper left of the page, then click VPC Infrastructure > Routing tables in the Network section.
3.  Select your VPC from the VPC drop-down menu.
4.  Click the routing table to open its details page, then click Edit.
5.  Clear the VPN gateway checkbox in the Accepts routes from (optional) section and click Save. Service routes propagated by the VPN gateway are removed.
6.  Click Edit again.
7.  Select VPN gateway in the Accepts routes from (optional) section and click Save. Service routes propagated by VPN gateway are generated.
Remember, the credentials you use must have the Global Administrator role in Microsoft Azure Directory. If you are not prompted for a user name and password, take note. You might be logged in to a Microsoft Sharepoint account already. If you are logged in to an account that you don't want to use for this connector, stop here. (Any account where you are logged in will be used automatically. And you cannot change the account configuration later.) Open a web browser in incognito mode and start this procedure over from step 1.

Discovery generates an enterprise application that it will register with the SharePoint organization that you specify. The enterprise application name has the format IBM App Connect_{unique name}.
7. Review the permissions that are associated with the enterprise application that Discovery will register, and then select Consent on behalf of your organization.

Zoom

![Permission request dialog that asks you to consent on behalf of your organization to allow the app to 1. Read user files. 2. Read items in all site collections. 3. Maintain access to data you have given it access. 4. View users' basic profile.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/spo-app-permission.png)

Figure 2. Discovery permission request dialog
8. Click Accept.
9. If you want to create a collection, you can name the collection, and then click Finish.

Otherwise, you can click Back to exit the collection creation process.



Now, anyone from your organization who works in a project that is hosted by the same Discovery service instance can create a collection by using the SharePoint Online connector.



 OAuth support revisions 

Support for the OAuth method of authentication was added with a software update in February 2022. If you want to update an existing connector to use OAuth instead of SAML, you must re-create the connector. You cannot change the authentication mechanism for an existing connector.
: Depending on [your account settings](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview), you can use public or private endpoints to manage categories programmatically. For information about endpoints per region, see [API endpoints](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-endpointsendpoints_api).

SERVICE_KEY
: Service key value. A service key is a unique code that is passed in an API request to identify the calling application or user. The service key is specific to a logging instance. For more information on how to generate a service key, see [Managing service keys](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keys).

KEY_NAME
: Name that you want to give the key. The maximum size of a name is 30 characters.





 Change the name of a key 

curl -X POST "https://API_ENDPOINT/v1/config/keys/KEY_ID"
-H 'content-type: application/json' -H 'servicekey: SERVICE_KEY' -d '{"name": "KEY_NAME"}'

Where:

API_ENDPOINT
: Depending on [your account settings](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview), you can use public or private endpoints to manage categories programmatically. For information about endpoints per region, see [API endpoints](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-endpointsendpoints_api).

SERVICE_KEY
: Service key value. A service key is a unique code that is passed in an API request to identify the calling application or user. The service key is specific to a logging instance. For more information on how to generate a service key, see [Managing service keys](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keys).
Reader As a reader, you can perform read-only actions within a service such as viewing service-specific resources. 
 Writer As a writer, you have permissions beyond the reader role, including creating and editing service-specific resources. 







 Internet of Things Platform 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use iotf-service for the service name.

Platform roles

Actions



Table 81. Platform roles - Internet of Things Platform
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions based on the resource this role is being assigned, including assigning access policies to other users. 
 Editor As an editor, you can perform all platform actions except for managing the account and assigning access policies. 
 Operator As an operator, you can perform platform actions required to configure and operate service instances, such as viewing a service's dashboard. 







 Infrastructure Service 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use is for the service name.

No supported roles.





 Regional Backup as a Service for VPC 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use is.backup-policy for the service name.

Platform roles

Actions



Table 83. Platform roles - Regional Backup as a Service for VPC
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can create, manage, retrieve and delete backup polices and plans, including assigning access policies to other users.
: Depending on [your account settings](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview), you can use public or private endpoints to manage categories programmatically. For information about endpoints per region, see [API endpoints](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-endpointsendpoints_api).

SERVICE_KEY
: Service key value. A service key is a unique code that is passed in an API request to identify the calling application or user. The service key is specific to a auditing instance. For more information on how to generate a service key, see [Managing service keys](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keys).

KEY_NAME
: Name that you want to give the key. The maximum size of a name is 30 characters.





 Change the name of a key 

curl -X POST "https://API_ENDPOINT/v1/config/keys/KEY_ID"
-H 'content-type: application/json' -H 'servicekey: SERVICE_KEY' -d '{"name": "KEY_NAME"}'

Where:

API_ENDPOINT
: Depending on [your account settings](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview), you can use public or private endpoints to manage categories programmatically. For information about endpoints per region, see [API endpoints](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-endpointsendpoints_api).

SERVICE_KEY
: Service key value. A service key is a unique code that is passed in an API request to identify the calling application or user. The service key is specific to a auditing instance. For more information on how to generate a service key, see [Managing service keys](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_keys).