vania-janet/multiturn-rag-retrieval-data huggingface dataset:
cat $HOME/<path-to-certificate>/cert.pem | base64 $FLAG





 Viewing and updating identities 

From the Wallet tab, click a tile to view, update, or remove an identity from the wallet. It might be necessary to update your identities if their certificates have expired, and they need to be issued new keys from the CA. You can also use this tab to delete keys from your console and your local system.

Clicking an identity opens a side panel that displays its certificates and private keys in base64 format. Click the download button ![Download](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/download.png) to export both the certificate and the private key as a .pem file to your local file system.

Zoom

![Export cert and private key](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/export_identity.png)

How to Export cert and private key

Click Update to change the identity name in the wallet or paste a new set of keys into the panel. Click Remove when you no longer need to use this identity and want to delete its keys.

IBM Blockchain Platform can auto-renew the enrollment (signing) certificates for the peer and ordering nodes and the peer TLS certificate. For the other certificates, you can see [certificate types and actions](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-cert-types) to learn on how to maintain them.

A one-stop solution is available for easy management and maintenance of your certificates; see [IBM Secrets Manager](https://www.ibm.com/cloud/secrets-manager) for details.





 Downloading certificates
Export this updated MSP, and in an out of band action, share the file with all of the members of the network who must import it into their console. It is important for them to import the updated MSP, so when they create a new channel, they are using the MSP definition with the latest admin certificate.



To verify that the update worked, open the MSP tile and view the updated expiration date.





 Step three: Associate new admin identity on peer or ordering service 

If the updated certificate is an admin certificate for a peer or ordering service, you need to update the node admin identity. Open the associated peer or ordering service and click the Associate identity for peer or Associate identity for ordering service and browse to the newly created identity from the wallet.

To verify that this update worked successfully on the peer, after you associate the identity, you should be able to see the list of channels that the peer is on and list the smart contracts that are installed on the peer.





 Step four: Update peer organization MSP on application channel 

As with all application channel updates, this update needs to be performed by a channel operator and the change will follow the channel update approval process according to the policy that was configured when the channel was created.

If the peer organization MSP was not originally created with the Node OU configuration enabled, you also need to update all application channels that include the MSP so that it uses the new admin certificate. When the Node OU configuration is enabled, the MSP uses the value of the OU inside the certificate to determine if the identity is an admin in addition to checking the admin section of the MSP definition.

Complete the following steps for a peer admin certificate:



1. Open the channel to be updated in the console.
2. Click Channel details and scroll down to Channel members.
3. Click the channel member that you want to update.
4. On the Update MSP definition panel, select the updated MSP and the original identity and click Update MSP definition. You must use the original identity for this step because it's currently the only one with permission to make channel updates. This action replaces the existing peer organization admin MSP definition with the updated MSP that includes the new admin certificate.
A verification method becomes inaccessible if a phone number or email address that's associated with your identity changes or you no longer have access to it. To reset a verification method, [open a support case](https://cloud.ibm.com/unifiedsupport/cases/form) and add a verification method that you can use to access the Verification methods and authentication factors page.
* How can I get a new QR code for MFA setup?

To get a new QR code for MFA setup, go to the [Verification methods and authentication factors](https://iam.cloud.ibm.com/mysecurity) page. From the Authentication factors section, click Show authentication factors > Add. Next, choose a type and select TOTP. Then, the new QR is available. After you scan the QR code, enter the TOTP that is generated by the authenticator app to confirm your choice. Now, each time you log in you provide the TOTP generated by the authenticator app that you just set up.
* How do I change the email address that is used for MFA?

You can update the email address that is used for MFA on the [Verification methods and authentication factors](https://iam.cloud.ibm.com/mysecurity) page. From the Authentication factors section, click Show authentication factors > Add. Select Email-based and enter the email address where you want to receive OTPs as an authentication factor. Then, enter the OTP you receive to confirm your choice. Next, click Complete. After you add the new factor, select the old email address, and click Remove.
* Can trusted profiles create user API keys?

If you use a trusted profile, you can't create a user API key. You can still create and manage all other API keys. For example, service ID API keys.

To create a user API key, your IAM ID and the IAM ID of the user that's requesting the user API key must be the same. When you apply a trusted profile, you take on the IAM ID of that profile. To create a user API key for your identity, log out of IBM Cloud and log back in without applying a trusted profile.
To update the context-based restrictions on your cloud resources, use the [ibmcloud cbr rule-update](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-rule-update-command) command. The following example updates description, allowed endpoint type, and network zone for a rule with the ID 30fd58c9b75f40e854b89c432318b4a2.

ibmcloud cbr rule-update 30fd58c9b75f40e854b89c432318b4a2 --description 'Example rule description' --service-name kms --context-attributes endpointType=private --zone-id 93de8d3f588ab2c457ff576c364d1145





 Updating rules by using the API 

To update restrictions to your cloud resources by creating rules, call the [Context-based restrictions API](https://cloud.ibm.com/apidocs/context-based-restrictions?code=nodereplace-rule). The following example replaces a rule with an updated version.



* Curl
* Java
* Python
* Go
* Node
"id" : "LambStew",
"error" : "conflict",
"reason" : "Document update conflict."
},
{
"id" : "7f7638c86173eb440b8890839ff35433",
"error" : "conflict",
"reason" : "Document update conflict."
}
]
Show more





 Bulk document validation and conflict errors 

The JSON returned by the _bulk_docs operation consists of an array of JSON structures, one for each document in the original submission. The returned JSON structure must be examined to ensure that all of the documents that were submitted in the original request were successfully added to the database.

The structure of the returned information is shown in the following tables:



Table 4. Structure of JSON returned

 Field Description Type 

 docs List of document objects Array of objects 



Each docs array object has the following structure:



Table 5. Structure for the docs array object

 Field Description Type 

 id Document ID String 
 error Error type String 
 reason Error string with extended reason String 



When a document (or document revision) is not correctly committed to the database because of an error, you must check the error field to determine error type and course of action. The error is one of [conflict](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-bulk-operationsconflict) or [forbidden](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-bulk-operationsforbidden).



 conflict 

The document as submitted is in conflict. If you used the default bulk transaction mode, then the new revision wasn't created. You must resubmit the document to the database.

Conflict resolution that uses the bulk docs interface is identical to the resolution procedures outlined in the [Conflicts](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-conflicts) documentation.





 forbidden 

Entries with this error type indicate that the validation routine that was applied to the document during submission returned an error.
curl -X PATCH --location --header "Authorization: Bearer {iam_token}" --header "Accept: application/json" --header "Content-Type: application/merge-patch+json" --data '{ "name": "{new_tool_name}", "parameters": {new_tool_parameters} }' "{base_url}/toolchains/{toolchain_id}/tools/{tool_id}"

import com.ibm.cloud.continuous_delivery.cd_toolchain.v2.CdToolchain;
import com.ibm.cloud.continuous_delivery.cd_toolchain.v2.model.;
...
CdToolchain toolchainService = CdToolchain.newInstance();
HashMap<String,Object> toolchainToolPrototypePatch = new HashMap<>();
toolchainToolPrototypePatch.put("name", {new_tool_name});
toolchainToolPrototypePatch.put("parameters", {new_tool_parameters});
UpdateToolOptions updateToolOptions = new UpdateToolOptions.Builder()
.toolchainId({toolchain_id})
.toolId({tool_id})
.toolchainToolPrototypePatch(toolchainToolPrototypePatch)
.build();
Response<ToolchainToolPatch> response = toolchainService.updateTool(updateToolOptions).execute();
ToolchainToolPatch tool = response.getResult();

const CdToolchainV2 = require('@ibm-cloud/continuous-delivery/cd-toolchain/v2');
const toolchainService = CdToolchainV2.newInstance();
...
(async() => {
const toolPatchModel = {
If you omit any required fields, the rule overwrites those missing fields as empty, and the rule might fail because some of those fields are required, regardless of whether they are changing the rule.

Updating requires the RULE-ID, not the rule name. Use the following command to list your rules and retrieve the relevant RULE-ID:

ibmcloud cbr rules

Delete a rule by using a command like:

ibmcloud cbr rule-delete <RULE-ID>





 Verifying your rule 

To verify that your rule is applied, go to the IBM Cloud® Dashboard and select the relevant instance from your Resource List. Within Recent Tasks, you see your rule's status.

The task of creating or modifying a rule goes into your instance's task queue. Depending on workload, it might take some time for your rule enforcement to complete.
The list of enumerated values for this property may expand in the future. Code and processes using this field must tolerate unexpected values. <br>Possible values: [attached,failed,pending,deleting,detaching,detached] 
 updated_at <br>date-time The date and time that this connection was last updated 





Table 4. Status codes

 Status code 

 201 The transit gateway connection was created successfully. 
 400 An invalid connection template was provided. 
 404 The specified Transit Gateway could not be found, the specified resource group could not be found, or the default resource group could not be found (if the resource group was not specified in the template). 
 409 The network being connected must either be in a location that is considered "local" to the specified Transit Gateway, or the specified Transit Gateway must be global. The network being connected cannot already be connected to another Transit Gateway. 





 Example response 

This example illustrates the response from a request for a cross-account connection:

{
"created_at": "2020-03-31T12:08:05Z",
"id": "1a15dca5-7e33-45e1-b7c5-bc690e569531",
"name": "example-connection",
"network_id": "crn:[...]",
"network_type": "vpc",
"status": "pending",
"updated_at": "2020-03-31T12:08:05Z"
}









 Perform actions on a requested connection 

After the original account has requested a cross-account connection, the other account must perform actions on a requested connection.



 Request 

To perform actions on a requested cross-account connection, set the following parameters:



Table 5. Query parameters for requesting a cross-account connection

 Query parameters Details 

 version <br>Required <br>string Requests the version of the API as of a date in the format YYYY-MM-DD. Any date up to the current date may be provided. Specify the current date to request the latest version.
* [Updating a blueprint through CLI](https://cloud.ibm.com/docs/schematics?topic=schematics-update-blueprintupdate-blueprint-cli)



* [Verifying blueprint update](https://cloud.ibm.com/docs/schematics?topic=schematics-update-blueprintverify-update)



* [Updating a blueprint environment using the UI](https://cloud.ibm.com/docs/schematics?topic=schematics-update-blueprintupdate-blueprint-ui)



* [Verify blueprint update using the UI](https://cloud.ibm.com/docs/schematics?topic=schematics-update-blueprintverify-bp-update-ui)



* [Updating a blueprint using the API](https://cloud.ibm.com/docs/schematics?topic=schematics-update-blueprintupdate-blueprint-api)



* [Verify blueprint create using the API](https://cloud.ibm.com/docs/schematics?topic=schematics-update-blueprintverify-bp-update-api)



* [Next steps](https://cloud.ibm.com/docs/schematics?topic=schematics-update-blueprintbp-update-nextsteps)



[Apply blueprint config changes to an environment](https://cloud.ibm.com/docs/schematics?topic=schematics-apply-blueprintapply-blueprint)



* [Running a blueprint apply through CLI](https://cloud.ibm.com/docs/schematics?topic=schematics-apply-blueprintapply-blueprint-cli)



* [Verify blueprint run apply success](https://cloud.ibm.com/docs/schematics?topic=schematics-apply-blueprintbp-verify-apply-cli)
![new-assemble-1.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/new-assemble-1.png)

c. Drag the invoke policy from the palette and drop it on the processing line beneath get /current. The invoke action is used to call an existing service from within an operation.
d. Update the action title to "invoke-current".
e. Update the URL field with https://myweatherprovider.mybluemix.net/current?zipcode=$(request.parameters.zipcode).

![new-assemble-invoke1.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/new-assemble-invoke1.png)

f. Drag the invoke policy from the palette and drop it on the processing line beneath get /today. g. Update its title to "invoke-today".
h. Update the URL field with https://myweatherprovider.mybluemix.net/today?zipcode=$(request.parameters.zipcode).

![new-assemble-invoke2.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/new-assemble-invoke2.png)
18. Close the action configuration panel. Save your API.



--------------------





 Test your API proxy 



1.
[Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg) for the field you want to update.
4. Click Save.

You can revert to the published state of your support information by clicking Revert changes.
5. Click Request approval when you're ready with your updates. The approval can take at least five business days.
6. After your request is reviewed and approved by the IBM Cloud team, publish your changes by clicking Publish approved changes.

Any changes that you don't publish are deleted after 60 days.



You can toggle between the updated and the published state of your support information. Toggle the switch on to review your updates, and toggle the switch off for the published state.





 Selecting your product's support provider by using the API 

You can programmatically select the support provider of your product by calling the [Partner Center Sell API](https://cloud.ibm.com/apidocs/partner-center-sellupdate-support) as shown in the following sample request. The example adds the third-party support provider type to your product:

curl --request PATCH --url https://product-
lifecycle.api.cloud.ibm.com/openapi/v1/products/9fab83da-98cb-4f18-
a7ba-b6f0435c9673/support --header 'Authorization: Bearer TOKEN' --header 'Content-Type:
application/json' --data '{
"support_type": "third-party"
}'

The details that you provide are displayed on your product details page in the catalog.





 Providing your product's support information by using the API 

You can programmatically provide the support information of your product by calling the [Partner Center Sell API](https://cloud.ibm.com/apidocs/partner-center-sellupdate-support) as shown in the following sample request.
"id" : "a931192f-b6a9-43d6-a59a-834f3003af7b",
"intermediate_included" : true,
"issuer" : "DigiCert",
"key_algorithm" : "RSA2048",
"labels" : "dev", "us-south" ],
"locks_total" : 0,
"name" : "my-imported-certificate",
"private_key_included" : true,
"secret_group_id" : "bfc0a4a9-3d58-4fda-945b-76756af516aa",
"serial_number" : "03:e2:c6:e4:0b:7d:30:e2:e2:78:1b:b9:13:fd:f0:fc:89:dd",
"secret_type" : "imported_cert",
"signing_algorithm" : "SHA256-RSA",
"state" : 1,
"state_description" : "active",
"updated_at" : "2022-10-05T21:33:11Z",
"validity" : {
"not_before" : "2020-10-05T21:33:11Z",
"not_after" : "2023-10-05T11:49:42Z"
},
"versions_total" : 1
}, {
"alt_names" : "s1.example.com", ".s2.example.com" ],
"common_name" : "example.com",
"created_by" : "iam-ServiceId-e4a2f0a4-3c76-4bef-b1f2-fbeae11c0f21",
"created_at" : "2020-10-05T21:33:11Z",
Check and make sure that true is displayed as the value of the SELECTED column for all crypto units in the service instance where you want to rotate the master key. If any crypto units in the service instance are not selected, select the crypto units by clicking the Add crypto units button and following the prompts.

You can work with only one service instance at a time. If any crypto units in other service instances are selected, click the Remove crypto units button to unselect.







 Rotating master keys using smart cards and the Management Utilities 

To rotate the master key, follow these steps:



1. To load the new master key parts to the new master key register, follow these steps:



1. Select the Master keys tab and click Load.
2. If prompted, insert an EP11 smart card with an administrator signature key that is defined to the selected crypto units in smart card reader 1, and enter the smart card PIN on the smart card reader PIN pad.
3. When prompted, enter the number of master key parts to be loaded. Only 2 or 3 master key parts are accepted.
4. When prompted, insert the EP11 smart card that contains the first master key part in smart card reader 2 and enter the smart card PIN on the smart card reader PIN pad.
5. Select the master key part to be loaded from the list of master key parts on the smart card.
6. Repeat substep 4 and 5 for each master key part to be loaded.



After all master key parts are loaded, the new master key register is in Full uncommitted state.
2. Commit the new master key by following these steps:



1. Click Commit to move the master key to the Full committed state.
2. If prompted, in smart card reader 1, insert an EP11 smart card with an administrator signature key that is defined to the selected crypto units and enter the smart card PIN on the smart card reader PIN pad. Repeat this operation if prompted for more EP11 smart cards with signature keys.



After the process is complete, the new master key register is in Full committed state.
3.
"type": "application/vnd.ibm.kms.key+json",
"algorithmType": "AES",
"createdBy": "user id ...<redacted>...",
"creationDate": "2020-06-18T20:34:39Z",
"lastUpdateDate": "2020-06-18T20:34:39Z",
"keyVersion": {
"id": "c024c2b3-2093-46e5-aabb-fdf8cbc14e44",
"creationDate": "2020-06-18T20:34:39Z"
},
"extractable": false,
"state": 1,
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:a192d603-0b8d-452f-aac3-f9e1f95e7411:key:c024c2b3-2093-46e5-aabb-fdf8cbc14e44"
}

 update the policy and rotate the key every 2 months
$ ibmcloud kp key policy-update rotation $KEY_ID -m 2 --output json

{
"createdBy": "user id ...<redacted>...",
"creationDate": "2020-06-18T20:35:41Z",
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:a192d603-0b8d-452f-aac3-f9e1f95e7411:policy:2427dbde-6cff-41eb-8b5a-ff26b038cafc",
"lastUpdateDate": "2020-06-22T19:13:00Z",
"updatedBy": "user id ...<redacted>...",
"dualAuthDelete": { "enabled": true
}
}
]

 attempt to delete the key - this fails
$ ibmcloud kp key delete 6a8a129b-0cd4-4667-ba57-b355a125a7ca

Deleting key: 6a8a129b-0cd4-4667-ba57-b355a125a7ca, from instance: a192d603-0b8d-452f-aac3-f9e1f95e7411...
FAILED
kp.Error:
correlation_id='8ad33eb2-7bbf-4b7a-a02e-221959920342',
msg='Conflict: 1 prior authorization(s) are required for deletion: Key could not be deleted. Please see "reasons" for more details.',
reasons='[AUTHORIZATIONS_NOT_MET: Number of authorizations required to delete is not met -
FOR_MORE_INFO_REFER: https://cloud.ibm.com/apidocs/key-protect]'

 disable the instance dual authorization policy
$ ibmcloud kp instance policy-update dual-auth-delete --disable

Updating instance policy...
OK

 attempt to delete the key - this fails because the key policy
How do I get access to upgrade my IBM Cloud account? 

You can't upgrade to a Pay-As-You-Go account.

  What’s happening 

When you try to upgrade your account from the [Account settings](https://cloud.ibm.com/account/settings) page in the IBM Cloud console, the following message is displayed:

> Looks like you don't have access to view this page. Contact the account owner for access.

  Why it’s happening 

To upgrade your account, you must have an access policy with the Editor role or higher on all account management services.

  How to fix it 

Contact the account owner to request access to upgrade your account. For more information, see [Upgrading your account](https://cloud.ibm.com/docs/account?topic=account-upgrading-account).
You may need to be cautious about upgrading peers and orderers to use the system channel removal features. Hyperledger Fabric v2.4 updated its chaincode version of Node.js to v16 and removed support for the earlier Node.js v12. If you are upgrading your peers and orderers to use the channel participation APIs, and are using Node.js v12 based chaincode, you must also incrementally upgrade the Node.js chaincode, as follows:



1. Upgrade any v1.4.x peers to v2.2.x (note that earlier Node.js v12 chaincode will continue to work, because Fabric v2.2.x provides both Node.js environments (v12 and v16)
2. Update your chaincode locally to use a Node.js v16.14.2 (or later v16.x.x) environment
3. Perform a [Fabric chaincode upgrade](https://hyperledger-fabric.readthedocs.io/en/release-2.2/chaincode_lifecycle.htmlupgrade-a-chaincode) on each channel where this chaincode is used
4. Upgrade your v2.2.x peers to Fabric v2.4.x