vania-janet/multiturn-rag-retrieval-data huggingface dataset:
No, you can't add users to child accounts.

You need to be invited to the child account and assigned the editor or administrator role for the User management service to add users to a child account.
* What are IBM Cloud projects?

As an enterprise, you use projects to ensure that the configuration of your deployable architecture is always compliant, cost effective, and secure. Projects are a named collection of configurations that are used to manage related resources and Infrastructure as Code (IaC) deployments across accounts.
* How do I add users to my project?

To add a user to a project, they must be a member of your account with correct IAM access roles assigned.

To assign access to the IBM Cloud Projects service, complete the following steps:



1. In the IBM Cloud console, click Manage > Access (IAM), and then select Users.
2. Click the user or access group that you want to assign access, then go to Access > Assign access.
3. For the service, select Project. Then, click Next.
4. Scope the access to All resources or Specific resources. Then, click Next.
5. Select any combination of roles or permissions, and click Review.
6. Click Add to add your policy configuration to your policy summary.
7. Click Assign.



In addition, users must be assigned the Editor and Manager role on the Schematics service and the Viewer role on the resource group for the project.
* How do I estimate project costs?

During the validation process, the starting costs for the project are estimated. You can view the cost details associated with the project from the validation modal after your changes to the configuration are saved and validated.
* Who has access to my project?

Any user that is a member of your account that is assigned access to the IBM Cloud Projects service, Schematics, and the resource group for your project can access your project.



Selling on IBM Cloud



* What are the different metering options for plans?

IBM Cloud® supports multiple models for aggregating service usage. Service providers measure various metrics on the created instances and submit those measures to the metering service.
If you have a Service ID that you want to use, select it. If not, select Create, enter a name and description, and click Create.
4. From the Service ID page, from the Access policies section, select Assign access.
5. From the Assign service ID additional access section,



1. Select Container Registry for type of access. Click Next.
2. Select the type of access: All resources or Specific resources. If you specify Specific resources, you can add attributes based on resource group, geography, region, resource type, resource ID, or resource name to further restrict access. If you select a certain resource group, make sure to select Viewer access for Resource group access. Click Next.
3. In the Roles and Actions section, select the type of access you want to grant. If you plan to use only images for your applications and jobs, select Reader. If you want to push the source code and images to Container Registry, then also select Writer. Click Review.
4. Click Add and then Assign.









 Step 2 Enabling Container Registry discovery 

To allow the Code Engine console to automatically discover Container registry, you must authenticate the service ID to the IAM Identity Service.



1. From the Service ID page, from the Access policies section, select Assign access.
2. From the Assign service ID additional access section,



1. Select IAM Identity Service for type of access. Click Next.
2. Select Specific resources for resource scope. Select Resource type as attribute type, keep string equals as operator and enter serviceid as value. Click Add a condition.
3. Select Resource ID as attribute type, keep string equals as operator and put the identifier of your service ID. You can find your service ID on the Details page for the service ID or in the browser URL when configuring it. Click Next.
4. In the Roles and Actions section, select Platform Operator access. Click Review
5. Click Add and then Assign.









 Step 3 Creating an API key for a service ID 

Create an API key for a service ID.



1.
// Enroll the admin user, and import the new identity into the wallet.
const enrollment = await ca.enroll({ enrollmentID: '<app_enroll_id>', enrollmentSecret: '<app_enroll_secret>' });
const identity = X509WalletMixin.createIdentity('<msp_id>', enrollment.certificate, enrollment.key.toBytes());
await wallet.import('user1', identity);
console.log('Successfully enrolled client "user1" and imported it into the wallet');

} catch (error) {
console.error(Failed to enroll "user1": ${error});
process.exit(1);
}
}
main();
Show more

Take a moment to study how this file works before we edit it. First, enrollUser.js imports the FileSystemWallet and X509WalletMixin classes from the fabric-network library.

const FabricCAServices = require('fabric-ca-client');
const { FileSystemWallet, X509WalletMixin } = require('fabric-network');

The file then uses the FileSystemWallet class to build a wallet on your local filesystem. You can edit the following line to store the wallet in a different location.

const wallet = new FileSystemWallet('../identity/user/isabella/wallet')

After you create the wallet, the code snippet uses the enroll ID and secret to enroll by using your organization CA. It then creates an identity for the signing certificate and private key and imports them into the wallet. Notice how the file passes your organization MSP ID into the wallet as well.

// Enroll the admin user, and import the new identity into the wallet.
const enrollment = await ca.enroll({ enrollmentID: '<app_enroll_id>', enrollmentSecret: '<app_enroll_secret>' });
Complete the [prerequisite steps](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-connector-sharepoint-onprem-cp4dconnector-sharepoint-onprem-cp4d-prereq) to add support.

When you enable this option, you must provide values for the following fields:

LDAP server URL
: The LDAP server URL to connect to, for example ldap://<ldap_server>:<port>.

LDAP binding username
: The username used to bind to the directory service. In most cases, this username is a distinguished name (DN). The logon name might sometimes work with Active Directory. But unlike the general Windows logon, it is case sensitive. The distinguished name always works.

LDAP binding user password
: The password used to bind to the directory service.

LDAP base DN
: The starting point for searching user entries in LDAP, for example CN=Users,DC=example,DC=com.

LDAP user filter
: The user filter to search user entries in LDAP. If unspecified, the default value is (userPrincipalName={0}).
12. If you want the crawler to extract text from images on the site, expand More processing settings, and set Apply optical character recognition (OCR) to On.

When OCR is enabled and your documents contain images, processing takes longer. For more information, see [Optical character recognition](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collectionsocr).
13. Click Finish.



The collection is created quickly. It takes more time for the data to be processed as it is added to the collection.

If you want to check the progress, go to the Activity page. From the navigation pane, click Manage collections, and then click to open the collection.



 Prerequisite steps for prior releases 

If you are using version 2.2.1 or earlier, then you must complete these extra steps before you can connect to the data source:
This tutorial does not configure attributes on identities, see [Registering identities](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-identitiesibp-console-identities-register) if you want to learn more. Click Register user.
4. After the organization admin has been registered, repeat this same process for the identity of the peer (also using the Org2 CA). For the peer identity, give an enroll ID of peer2 and a secret of peer2pw. This is a node identity, so select peer as the Type. You can ignore the Maximum enrollments field and, on the next panel, do not assign any Attributes, as before.
5. You can also register identities of type orderer with the TLS CA. Completing this optional step for your orderer's admin identity allows viewing additional channel details for the orderer nodes that use this identity. Repeat steps 1-2 above, changing the Certificate Authority drop-down selection from Root Certificate Authority to TLS Certificate Authority.



Registering these identities with the CA is only the first step in creating an identity. You will not be able to use these identities until they have been enrolled. For the org2admin identity, this will happen during the creation of the MSP, which we will see in the next step. In the case of the peer2 identity, it happens during the creation of the peer.

Task: Register users



Table 4. Using your CA to register user

 Field Description Enroll ID Secret Type 

 Create CA CA admin admin adminpw client 
 Register users Org2 MSP Admin org2admin org2adminpw admin 
 Peer identity peer2 peer2pw peer 







 Creating the peer organization MSP 

Now that we have created the peer's CA and used it to register our organization identities, we need to create a formal definition of the peer's organization, which is known as the Membership Services Provider (MSP) definition. Many peers can belong to an organization. You do not need to create a new organization every time you create a peer.
If there are multiple hosts, download the template, complete the appropriate fields, and then upload the template.
4. Select the Wave name to enter source and target information.
5. Select the "+" sign.
6. Add source IP address or FQDN and add source username.
7. Target Type = Existing system
8. Sync Type = Direct sync
9. Add target IP address or FQDN.
10. Add a target-friendly name, and add a target username.
11. Start the migration.



The username field for Linux environments is root. The username field for Windows environments is SYSTEM.





 Step 7: Validate your migration 

After your server migration, validate your compute resources, such as applications and data, and update or validate the following:



1. Access the target server.
2. Check partitions and volumes.
3. Check the applications.
4. Install any test application in the target server.
5. Check networking routes.
6. Check or update your yum repos, application settings, and configuration file.
7. Check or update application or operating system licenses.
8. Remove the RMM SSH key.
Optional: Expand the Proxy settings section to add information that is required if you are using a proxy server to access the data source server.



* Enable proxy settings: Set the switch to On, and then add the following information:

Username
: The proxy server username to use to authenticate, if the proxy server requires authentication. If you do not know your username, you can get it from the administrator of your proxy server.

Password
: The proxy server password to use to authenticate, if the proxy server requires authentication. If you do not know your password, you can get it from the administrator of your proxy server.

Proxy server host name or IP address
: The hostname or the IP address of the proxy server.

Proxy server port number
: The network port that you want to connect to on the proxy server.



9. In the Object Types* section, specify the object types to crawl.

The default behavior is to crawl all object types.



* For custom object names, append __c to match the Salesforce API convention for custom object names. For example, to crawl MyCustomObject, specify MyCustomObject__c.
* Do not specify a comment object, such as FeedComment, CaseComment, IdeaComment, without also specifying the corresponding root object, such as FeedItem, Case, and Idea.
* If you specify a tag object, you must also specify its parent. For example, do not specify the AccountTag object without also specifying the Account object.



10. If you want the crawler to extract text from images on the site, expand More processing settings, and set Apply optical character recognition (OCR) to On.

When OCR is enabled and your documents contain images, processing takes longer. For more information, see [Optical character recognition](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-collectionsocr).
11. Click Finish.



The collection is created quickly. It takes more time for the data to be processed as it is added to the collection.

If you want to check the progress, go to the Activity page.
You will specify this value as the {url}.
3. Copy the bearer token also. You will need to pass the token when you make an API call.
4. From the dialog builder in the user interface, add a search skill response type to a dialog node.
5. Make a note of the unique ID of the assistant to which you added the dialog that you edited in the previous step.



* To get the ID for an assistant from the user interface, click the more menu on the tile for the assistant, and then click Settings. Click API Details.



6. Start a session, which is kind of like a new conversation, in which you will make the user input request.

Use a POST request like this to create the session, and pass an empty body with the request:

curl -H "Authorization: Bearer {token}" -X POST "{url}/v2/assistants/{assistant_id}/sessions?version=2020-04-01 -k"



* {token} is the token you copied earlier.
* {assistant_id} is the assistant ID you copied earlier.



7. Now, send a user input request that triggers the dialog node with the search skill response type.

For example, to test a search that is initiated from the greeting node, you might use a POST request like this:

curl -H "Authorization: Bearer {token}" -H "Content-Type:application/json" -X POST -d "{"input": {"text": "Hello"}}" "https://{my-cluster-hostname}/assistant/api/v2/assistants/{assistant_id}/sessions/{session_id}/message?version=2019-02-28"



* {token} is the token that is generated in Step 3.
* {assistant_id} is the assistant ID you copied in Step 2.
* {session_id} is the ID of the session that you created in the previous step.



8. Review the response to make sure it includes the search results that you expect.
9. Repeat this procedure to submit queries that trigger the search.
"picture": "https://lh3.googleusercontent.com/-XdUIqdbhg/AAAAAAAAI/AAAAAAA/42rbcbv5M/photo.jpg",
"gender": "male",
"locale": "en",
"idpType": "google"
}
}
]
3. Verify that the sub claim exactly matches the sub claim in the identity token. If these do not match, do not use the returned information. To learn more about token substitution, see the [OIDC specification](https://openid.net/specs/openid-connect-core-1_0.htmlTokenSubstitution).



If changes are made by an external identity provider, you can get the updated information when your users log in again. Your new tokens retrieve the most up-to-date data.





 Accessing the /attributes endpoint 

Depending on your configuration, attributes are encrypted and saved as part of a user profile when a user interacts with your application. The interaction might be a user signing in or setting a preference in your app. To access the attributes, pass an access token through an API method.



* Curl
* Java
* Node
* Swift
* Swift



curl -X GET 'https://<region>.appid.cloud.ibm.com/api/v1/attributes'
-H 'Accept: application/json'
-H 'Authorization: Bearer <accessToken>'

void setAttribute(@NonNull String name, @NonNull String value, UserAttributeResponseListener listener);
void setAttribute(@NonNull String name, @NonNull String value, @NonNull AccessToken accessToken, UserAttributeResponseListener listener);

void getAttribute(@NonNull String name, UserAttributeResponseListener listener);
User data Paste your user data to the User data (optional) field or click Import user data to upload from your user data. For example, you can enable SSH by adding the following script to the User data (optional) field. For more information about user data, see [User data](https://cloud.ibm.com/docs/vpc?topic=vpc-user-data). 
 Trusted Platform Module (TPM) Click the toggle to enable Trusted Platform Module capabilities. Then, select the mode that you want to use. For more information, see [Secure boot with Trusted Platform Module (TPM)](https://cloud.ibm.com/docs/vpc?topic=vpc-secure-boot-tpm&interface=ui). 
 Secure boot Click the toggle to enable secure boot. For more information, see [Secure boot with Trusted Platform Module (TPM)](https://cloud.ibm.com/docs/vpc?topic=vpc-secure-boot-tpm&interface=ui). 



For x86 architecture-based bare metal servers, the DHCP response for all interfaces (PCI or VLAN) includes a gateway. So, if you create multiple interfaces on different subnets, consider a static IP configuration or use separate network namespaces to handle the different gateways.





 Creating a bare metal server by using the API 

You can create a bare metal server by using the API. Use the following steps to create a bare metal server by using the API.



 Before you begin 



1. Make sure that you set up your API environment. For more information, see [Setting up your API and CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environment).

To learn more about the API, click Get sample API call on the create pages in IBM Cloud® console. You can view the correct sequence of API requests and better understand actions and their dependencies.
2. Make sure that you create a VPC and a subnet before you create a bare metal server.







 Gathering information for the bare metal server
{region}.databases.cloud.ibm.com/v4/ibm/deployments/{id}/users' -H "Authorization: Bearer $APIKEY" -H "Content-Type: application/json" -d '{"username":"jane_smith", "password":"newsupersecurepassword"}'

Once the task finishes, you can retrieve the new user's connection strings, from the /users/{userid}/connections endpoint.





 Adding users in the Service Credentials UI 

Creating a new user from the CLI doesn't automatically populate that user's connection strings into Service Credentials. If you want to add them there, you can create a new credential with the existing user information.

Enter the username and password in the JSON field Add Inline Configuration Parameters, or specify a file where the JSON information is stored. For example, putting {"existing_credentials":{"username":"Robert","password":"supersecure"}} in the field generates Service Credentials with the username "Robert" and password "supersecure" filled into connection strings.

Generating credentials from an existing user does not check for or create that user.







 Connection String Breakdown 



 The Postgres Section 

The "postgres" section contains information that is suited to applications that make connections to Databases for EnterpriseDB.



Table 1. postgresql/URI connection information

 Field Name Index Description 

 Type Type of connection - for Databases for EnterpriseDB, it is "URI" 
 Scheme Scheme for a URI - for Databases for EnterpriseDB, it is "postgresql" 
 Path Path for a URI - for Databases for EnterpriseDB, it is the database name. The default is ibmclouddb. 
 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
ibmcloud iam access-group-users example_group







 ibmcloud iam access-group-user-add 

Add users to an access group:

ibmcloud iam access-group-user-add GROUP_NAME USER_NAME [USER_NAME2...]



 Examples 

Add user name@example.com to access group example_group:

ibmcloud iam access-group-user-add example_group name@example.com







 ibmcloud iam access-group-user-remove 

Remove a user from an access group:

ibmcloud iam access-group-user-remove GROUP_NAME USER_NAME



 Examples 

Remove user name@example.com from access group example_group:

ibmcloud iam access-group-user-remove example_group name@example.com







 ibmcloud iam access-group-user-purge 

Remove user from all access groups:

ibmcloud iam access-group-user-purge USER_NAME [-f, --force]



 Command options 

-f, --force
: Delete without confirmation.





 Examples 

Remove user name@example.com from all access groups:

ibmcloud iam access-group-user-purge name@example.com -f







 ibmcloud iam access-group-service-ids 

List service IDs in an access group:

ibmcloud iam access-group-service-ids GROUP_NAME



 Examples 

List all service IDs in access group example_group:

ibmcloud iam access-group-service-ids example_group







 ibmcloud iam access-group-service-id-add 

Add service ID to an access group:

ibmcloud iam access-group-service-id-add GROUP_NAME SERVICE_ID_NAME [SERVICE_ID_NAME2...]



 Examples 

Add service ID example-service to access group example_group:

ibmcloud iam access-group-service-id-add example_group example-service







 ibmcloud iam access-group-service-id-remove 

Remove a service ID from an access group:
Assign the custom roles to the normal user service ID 

To assign the custom roles that are defined in [Step 1](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-best-practice-pkcs11-accessstep1-create-custom-roles) to the normal user service ID, follow these steps:

To assign access to the keystores for the normal user, follow these steps:



1. From the menu bar, click Manage > Access (IAM), and select Service IDs to browse the existing service IDs in your account.
2. Hover your mouse over the Normal user service ID, and click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/icons/action-menu-icon.svg) to open a list of options.
3. From the options menu, click Assign access.
4. Click Access policy.
5. Under Service, select Hyper Protect Crypto Services and click Next.
6. Under Resources, select Specific resources.
7. Select the Service Instance ID attribute type, enter the Hyper Protect Crypto Services service instance ID that you want to grant access to, and click Next.
8. Under Roles and actions, check the boxes for Key operator and click Next.
9. (Optional) Under Conditions (optional), click Review to check the access policy.
10. After confirmation, click Add > Assign.







 3. Assign the custom roles to the anonymous user service ID 

To assign the custom roles that are defined in [Step 1](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-best-practice-pkcs11-accessstep1-create-custom-roles) to the anonymous user service ID, follow these steps:

To assign access to the keystore for the anonymous user, follow these steps:



1.