vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Any traffic that is routed to these interfaces with [user-defined routes](https://cloud.ibm.com/docs/vpc?topic=vpc-create-vpc-route) is encrypted. For more information, see [About VPN gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpn).







 30 October 2020 



 For all version dates 



* Custom routing tables are now supported in the VPC API. This feature controls where network traffic is directed on a per-subnet basis. Explore new API methods for [routing tables](https://cloud.ibm.com/apidocs/vpclist-vpc-routing-tables) and [routes](https://cloud.ibm.com/apidocs/vpccreate-vpc-routing-table-route). This feature subsumes the [VPC routing API](https://cloud.ibm.com/apidocs/vpclist-all-routes-in-the-vpc-s-default-routing-table), which remains supported but is deprecated and might be removed in a future API release.
* Virtual private endpoint gateways. Use [virtual private endpoint gateways](https://cloud.ibm.com/apidocs/vpclist-endpoint-gateways) to connect to supported IBM Cloud services from your VPC network by using the IP addresses of your choice, which is allocated from a subnet within your VPC. For more information, see [About virtual private endpoint gateways](https://cloud.ibm.com/docs/vpc?topic=vpc-about-vpe).
* VPC network interfaces. IP anti-spoofing checks had already been provided for enhanced security. However, certain use cases, such as having a virtual server instance act as a network gateway, require selective disabling of these checks.
To limit API requests to the instance to take place only through a private network, use private-only. Keep in mind that the Secrets Manager service UI is not accessible for private-only instances. 



5. (Optional) Verify that that the service instance was created successfully.

ibmcloud resource service-instance <instance_name>

Provisioning a Secrets Manager instance can take 5 - 15 minutes to complete.







 Viewing your endpoint URLs 

The service endpoint URLs are different for private and public network connections. You can find your service endpoint URLs in the Endpoints page of the Secrets Manager UI. For more information about retrieving your service endpoint URLs programmatically, see [Regions and endpoints](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-endpointsview-endpoint-urls).
"request_id": "d567207f-b5e6-fc35-086e-fbc465bf3678",
"lease_id": "",
"lease_duration": 0,
"renewable": false,
"data": {
"roles": [
{
"created_by": "iam-ServiceId-b7ebcf90-c7a9-495b-8ce8-bbf33cb95ca0",
"creation_date": "2020-10-09T17:13:47Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/791f5fb10986423e97aa8512f18b7e65:e415e570-f073-423a-abdc-55de9b58f54e::",
"description": "My test IAM credential that is assigned to a secret group.",
"id": "091ca93f-5c99-4078-9d7e-4801143030fd",
"labels":
"test",
"us-south"
],
"last_update_date": "2020-10-09T17:13:47Z",
"name": "test-iam-credential-in-group",
"secret_group_id": "9ab2250f-a369-4e07-ade7-d417d63ad587",
"secret_type": "IAM_CREDENTIALS",
"state": 1,
"state_description": "Active",
"ttl": 3600
},
{
"created_by": "iam-ServiceId-b7ebcf90-c7a9-495b-8ce8-bbf33cb95ca0",
The email address must be escaped. For example, myTest%40yahoo.com instead of myTest@yahoo.com.

Alternatively, you can use the [Management APIs](https://us-south.appid.cloud.ibm.com/swagger-ui//Config/getAuditStatus). Your output would look similar to the following JSON object:

{
"users": [
{
"idp": "cloud_directory",
"id": "1e123399-3499-4a5c-b5a9-93843a91dc80"
},
{
"idp": "cloud_directory",
"id": "2a7abbe5-0fce-402e-9ddf-265246b415c8"
}
]
}
3. Search for a cloud_directory:id value in the target.name_str field in the Activity Tracker console.
Access for operations on the production environment can be set up in a trusted profile named Operator-Profile. This way, the developer can change job roles by logging in and applying the Operator-Profile when they need to take any operation actions on the CustApp in production.

If you have administrator access through a trusted profile, it is not recommended to invite users to an account while the profile is applied. Users should be invited by true account owners or administrators, or an error might occur.

For more information about IAM access and the available features, see [How IBM Cloud IAM works](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-iamoverview).
When you call the API, replace the ID variables and IAM token with the values that are specific to your Secrets Manager instance.

You can store metadata that are relevant to the needs of your organization with the custom_metadata and version_custom_metadata request parameters. Values of the version_custom_metadata are returned only for the versions of a secret. The custom metadata of your secret is stored as all other metadata, for up to 50 versions, and you must not include confidential data.

curl -X POST
-H "Authorization: Bearer {iam_token}" -H "Accept: application/json" -H "Content-Type: application/json" -d '{
"name": "example-private-certificate",
"description": "Description of my private certificate",
"secret_type": "private_cert",
"secret_group_id": "bfc0a4a9-3d58-4fda-945b-76756af516aa",
"labels": [
"dev",
"us-south"
],
"certificate_template": "test-certificate-template",
"common_name": "localhost",
"alt_names": [
"alt-name-1",
"alt-name-2"
],
"ip_sans": "127.0.0.1",
"uri_sans": "https://www.example.com/test",
"ttl": "2190h",
"rotation": {
"auto_rotate": true,
"interval": 1,
"unit": "month"
},
"custom_metadata": {
"metadata_custom_key": "metadata_custom_value"
},
"version_custom_metadata": {
"custom_version_key": "custom_version_value"
}
}' "https://{instance_ID}.{region}.secrets-manager.appdomain.cloud/api/v2/secrets"
Currently, the revoke action is supported for private_cert secrets only.
* Updated the [Get a version of a secret](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2get-secret-version) method that can be used to retrieve the previous version of a secret. This API now supports private_cert secrets in addition to imported_cert and public_cert.
* Updated the [Add a configuration](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2create-config-element), [List configurations](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2get-config-elements), [Update a configuration](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2update-config-element), [Get a configuration](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2get-config-element), and [Remove a configuration](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2delete-config-element) methods. These APIs now support private_cert secrets in addition to public_cert.
* Added the [Invoke an action on a configuration](https://cloud.ibm.com/apidocs/secrets-manager/secrets-manager-v2action-on-config-element) method that be used to run operations on specific configuration elements, for example root or intermediate certificate authorities. Currently, this API supports private_cert secrets only.







 3 February 2022 

This release includes the following update:
Example: If you assigned a Reader service access role, the service ID can list pods in your Red Hat OpenShift project.

oc get pods

Example: If you assigned a Manager service access role, the service ID can list the users in your Red Hat OpenShift cluster. The ID of your IAM service ID is in the Identities output. Other individual users might be identified by their email address and IBMid.

oc get users

Example output

NAME UID FULL NAME IDENTITIES
IAM dd44ddddd-d4dd-44d4-4d44-4d44d444d444 IAM:iam-ServiceId-bbb2b2b2-2bb2-2222-b222-b2b2b2222b22
IAMfirst.last@email.com 55555ee5-e555-55e5-e5e5-555555ee55ee IAM:IBMid-666666FFF6
"id": "keyreact",
"typeURI": "service/security/account/user",
"name": "",
"host": {
"address": "192.0.2.0/24172",
"agent": "grpc-go/1.22.1"
},
"credential": {
"type": "token"
}
},
"target": {
"id": "crn:v1:staging:public:is:us-south-1:a/82a90f2e-39e1-4a18-a8dc-6ebc17b61d7f::volume:cc6d2924-3cd2-459c-bb5e-9e84287fb530",
"typeURI": "is.volume/volume",
"name": "my-at-rewrap-encrypted-volume1",
"host": {}
},
"observer": {
"name": "ActivityTracker"
},
"reason": {
"reasonCode": 200,
"reasonType": "OK"
},
"severity": "normal",
"requestData": {
"account_id": "82a90f2e-39e1-4a18-a8dc-6ebc17b61d7f",
"action": "is.volume.volume.update",
"crn": "crn:v1:staging:public:is:us-south-1:a/82a90f2e-39e1-4a18-a8dc-6ebc17b61d7f::volume:cc6d2924-3cd2-459c-bb5e-9e84287fb530",
"generation": "gc",
"common_name": "example.com",
"alt_names": [
"www.example.com"
],
"labels": [
"dev",
"us-south"
],
"rotation": {
"auto_rotate": true,
"interval": 90,
"unit": day
}
}'
Show more





 Example responses 

A request to create an arbitrary secret in the default secret group returns the following response:

{
"request_id": "8c047529-de3a-a79d-7c2f-c382a8e75312",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-15T22:34:53Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0:secret:a6972127-35ad-b36f-aac8-0223f0475cb6",
"description": "Extended description for my secret.",
"expiration_date": "2030-04-01T09:30:00Z",
"id": "a6972127-35ad-b36f-aac8-0223f0475cb6",
"labels": [
"dev",
"us-south"
],
"url": "https://yourphoto.com/yourphoto.jpeg"
}
]
},
"context":{
"global":{
"system":{
"user_id":"00000000000000000000000000000000"
}
},
"integrations":{
"text_messaging":{
"assistant_phone_number":"+12223334444",
"private":{
"user_phone_number":"+14443332222",
"request_id":"00000000-0000-0000-0000-000000000000",
"ip_address":"172.10.10.10"
}
}
}
}
}
}
Show more

This example shows a stateful /message request sent by a custom channel application and including a single media attachment.



* Python
* Node



response=service.message(
assistant_id='{assistant_id}',
session_id='{session_id}',
input={
'message_type': 'text',
'text': 'Hello',
'attachments': [
{
'media_type': 'image/jpeg',
'url': 'https://yourphoto.com/yourphoto.jpeg'
}
]
}
).get_result()

print(json.dumps(response, indent=2))

Show more

service
.message({
assistant_id: '{assistant_id}',
session_id: '{session_id}',
input: {
message_type: 'text',
text: 'Hello',
attachments: [
{
'media_type': 'image/jpeg',
2020/01/10 21:27:50 Terraform plan | resource_group_id: "1e9b3e987aff4e32a541fe36b289347d"
2020/01/10 21:27:50 Terraform plan | resource_group_name: <computed>
2020/01/10 21:27:50 Terraform plan | resource_name: <computed>
2020/01/10 21:27:50 Terraform plan | resource_status: <computed>
2020/01/10 21:27:50 Terraform plan | service: "databases-for-postgresql"
2020/01/10 21:27:50 Terraform plan | service_endpoints: "public"
2020/01/10 21:27:50 Terraform plan | status: <computed>
2020/01/10 21:27:50 Terraform plan | tags.: "2"
2020/01/10 21:27:50 Terraform plan | tags.1852302624: "tag2"
2020/01/10 21:27:50 Terraform plan | tags.4151227546: "tag1"
2020/01/10 21:27:50 Terraform plan | users.: "1"
2020/01/10 21:27:50 Terraform plan | users.3114612762.name: "user123"
2020/01/10 21:27:50 Terraform plan | users.3114612762.password: <sensitive>
2020/01/10 21:27:50 Terraform plan | version: <computed>
2020/01/10 21:27:50 Terraform plan | whitelist.: "2"
2020/01/10 21:27:50 Terraform plan | whitelist.1413716549.address: "172.16.2.0/24"
2020/01/10 21:27:50 Terraform plan | whitelist.1413716549.description: "subnet2"
2020/01/10 21:27:50 Terraform plan | whitelist.3438994501.address: "172.16.1.0/24"
"api_token": "crn:v1:bluemix:public:secrets-manager:us-south:a/9bb43e401a7a87d15145da761da98571:604de62c-c04f-3f5e-b7e8-4acafe0ecde7:secret:5ec17023-b631-fbcb-ef9c-4f2eb01f1dda",
"channel_name": "my_slack_channel_name",
"team_url": "my_slack_team_name",
}
createToolOptions := toolchainClient.NewCreateToolOptions("01234567-89ab-cdef-0123-456789abcdef", "slack")
createToolOptions.SetParameters(slackParameters)
slackTool, response, err := toolchainClient.CreateTool(createToolOptions)







 Specifying secrets references with Terraform 

You can work with secure properties with secrets reference values in Terraform.



 Using secrets references by name 

The following example shows a complete set of resources for a Key Protect service instance, a standard key (Slack webhook), a toolchain, an IAM service-to-service authorization policy, a Key Protect tool integration, and a Slack tool integration that references the webhook secret by name.

This example also includes an ibm_kms_key standard key resource with a payload that is set to the base64-encoded Slack webhook secret. It shows the relationship between the name of the key and the value of the secrets reference within the Slack tool integration resource. In practice, it is more secure to create the standard key ahead of time from a separate Terraform project or other process to which only limited, authorized personnel have access.

variable "slack_webhook" {}
variable "slack_channel" {}
variable "slack_team" {}

data "ibm_resource_group" "rg" {
name = "default"
}
* Client secret - Enter the client secret required for authenticating the Client ID provided earlier.

Client ID and Client secret can be fetched from System Oauth -> Application Registries. This is inside your Event Notifications instance console (you can search by clicking on "All"). Make sure it is in active state and applicable for connecting to external clients.



4. Click Add.







 Event Notifications severity (ibmenseverity) to ServiceNow severity mapping 



Table 1. Event Notifications severity (ibmenseverity) to ServiceNow severity mapping

 Event Notifications severity (ibmenseverity) ServiceNow severity - Impact ServiceNow severity - Urgency ServiceNow severity - Priority 

 Critical 1 1 1 
 High 1 2 2 
 Medium 2 2 3 
 Low 2 3 4 
 Anything Else 3 3 4 







 ServiceNow retry policy 

When calling a webhook, issues such as network errors and application glitches can cause the requests to fail. A retry is used to provide resiliency to external requests. Attempt to retry the requests in such situations by using the following values:



* Limit = 60 seconds: total time that the service retries.
* Step = 5 seconds: after each failure, the service waits 5 seconds before retrying. This delay prevents bombarding of the external services (webhook).



In addition, the following timeout conditions cause the ServiceNow call to fail:



* A connection timeout of 10 seconds
* A response timeout of 60 seconds



If a call to the ServiceNow webhook URL fails even after retry attempts, the notification is lost.
},
"profile": {
"name": "custom"
},
"encryption_key":{
"crn":"crn:[...]"
},
"resource_group": {
"id": "2d1bb5a8-40a8-447a-acf7-0eadc8aeb054"
}
}'

A successful response looks like this:

{
"capacity": 50,
"created_at": "2022-06-14T23:16:53.000Z",
"crn": "crn:[...]",
"encryption": "user_managed",
"encryption_key": {
"crn": "crn:[...]"
},
"health_reasons": [],
"health_state": "ok",
"href": "https://us-south.iaas.cloud.ibm.com/v1/volumes/2d1bb5a8-40a8-447a-acf7-0eadc8aeb054",
"id": "2d1bb5a8-40a8-447a-acf7-0eadc8aeb054",
"iops": 100,
"name": "my-volume-4",
"profile": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/volume/profiles/custom",
"name": "custom"
},
"resource_group": {
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/4bbce614c13444cd8fc5e7e878ef8e21",
"id": "4bbce614c13444cd8fc5e7e878ef8e21",
"id": "0767-16871e0f-c43a-4b6e-8491-a3e075362046",
"name": "yapping-extract-reawake-bullhorn",
"resource_type": "subnet_reserved_ip"
},
{
"address": "10.241.64.12",
"href": "https://us-east.iaas.cloud.ibm.com/v1/subnets/0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024/reserved_ips/0767-a7db5d37-42cf-473e-ab27-07b679d64ceb",
"id": "0767-a7db5d37-42cf-473e-ab27-07b679d64ceb",
"name": "dioxide-stylized-headway-despise",
"resource_type": "subnet_reserved_ip"
}
],
"provisioning_status": "update_pending",
"public_ips": [],
"subnets": [
{
"id": "0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024",
"href": "https://us-east.iaas.cloud.ibm.com/v1/subnets/0767-064498f3-4df5-4fa5-b2ed-de5a3bfea024",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-15T22:43:36Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0:secret:2bd4c8fc-c1e4-f9d7-8026-6c04610f051f",
"description": "Extended description for my secret.",
"expiration_date": "2020-12-31T00:00:00Z",
"id": "2bd4c8fc-c1e4-f9d7-8026-6c04610f051f",
"labels": [
"dev",
"us-south"
],
"last_update_date": "2020-12-15T22:43:36Z",
"name": "test-username-password",
"secret_data": {
"password": "cloudy-rainy-coffee-book",
"username": "user123"
},
"secret_type": "username_password",
"state": 1,
"state_description": "Active",
"versions": [
{
"auto_rotated": false,
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
The private worker installation script pulls required images from the global IBM Cloud® Container Registry. It pulls the most recent images of pipeline private workers and respective Tekton framework images that include fixes for any vulnerability found.

The image URL for the pipeline private worker is icr.io/continuous-delivery/pipeline/pipeline-private-worker:<agent version>.



Table 4. Private Worker images

 Pipeline private worker image version IBM Cloud® Container Registry version Known vulnerabilities 

 0.15.0 icr.io/continuous-delivery/pipeline/pipeline-private-worker:0.15.0 <br><br> * <br><br><br> 



The private worker installation also pulls the following supporting open source images to the cluster:

icr.io/continuous-delivery/pipeline/tekton/controller
icr.io/continuous-delivery/pipeline/tekton/git-init
icr.io/continuous-delivery/pipeline/tekton/entrypoint
icr.io/continuous-delivery/pipeline/tekton/nop
icr.io/continuous-delivery/pipeline/tekton/sidecarlogresults
icr.io/continuous-delivery/pipeline/tekton/imagedigestexporter
icr.io/continuous-delivery/pipeline/tekton/workingdirinit
icr.io/continuous-delivery/pipeline/tekton/cloud-sdk
icr.io/continuous-delivery/pipeline/tekton/busybox
icr.io/continuous-delivery/pipeline/tekton/powershell
icr.io/continuous-delivery/pipeline/tekton/resolvers
icr.io/continuous-delivery/pipeline/tekton/webhook

The private worker agent also uses these internal images:

icr.io/continuous-delivery/pipeline/pipeline-private-worker-util
icr.io/continuous-delivery/pipeline/tekton/kubectl-jq
icr.io/continuous-delivery/pipeline/tekton/ubi



 Support for previous Delivery Pipeline Private Worker images
"href" : "https://us-south.secrets-maanger.cloud.ibm.com/88b75b20-aa21-4174-85c9-1feb3cc93c9a/api/v2/secrets?offset=150&limit=50"
},
"offset" : 100,
"secrets" : [ {
"alt_names" : "s1.example.com", ".s2.example.com" ],
"common_name" : "example.com",
"created_at" : "2020-10-05T21:33:11Z",
"created_by" : "iam-ServiceId-e4a2f0a4-3c76-4bef-b1f2-fbeae11c0f21",
"crn" : "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:f1bc94a6-64aa-4c55-b00f-f6cd70e4b2ce:secret:a931192f-b6a9-43d6-a59a-834f3003af7b",
"custom_metadata" : {
"metadata_custom_key" : "metadata_custom_value"
},
"description" : "Extended description for this secret.",
"downloaded" : false,
"expiration_date" : "2023-10-05T11:49:42Z",
"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",
Secret key reference (user): kafka-subscription-secret.username
Secret key reference (password): kafka-subscription-secret.password
Ready: true

Conditions:
Type OK Age Reason
ConnectionEstablished true 24s
InitialOffsetsCommitted true 24s
Ready true 24s
Scheduled true 24s
SinkProvided true 24s

Events:
Type Reason Age Source Messages
Normal FinalizerUpdate 26s kafkasource-controller Updated "mykafkasubscription" finalizers







 Sending events to the receiving app with the CLI 

Now that your Kafka event subscription, which references the kafka-receiver-app application, is created, use the kafka-sender-app to send message events to the receiver application.



1. Obtain the public URL of the destination app, kafka-sender-app by using the [ibmcloud ce app get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-get) command with the --output url option to find the URL of your app.

ibmcloud ce app get -n kafka-sender-app --output url

Example output

https://kafka-sender-app.abcdabcdabc.us-south.codeengine.appdomain.cloud
2. Run the Kafka event producer app, kafka-sender-app to send events to the destination Code Engine application. Call the kafka-sender-app application with curl and specify values for the topic and the number of messages. Use the output of the ibmcloud ce app get command to find the public URL of your app. Be sure to wrap the value to curl in quotation marks to ensure that it is treated as a single string.

curl "<public_URL_of_Kafka_sender_app>?topic=<your_topic_name>&num=<number_of_messages_to_produce>"

For example,
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0:secret:a6972127-35ad-b36f-aac8-0223f0475cb6",
"description": "Extended description for my secret.",
"expiration_date": "2030-04-01T09:30:00Z",
"id": "a6972127-35ad-b36f-aac8-0223f0475cb6",
"labels": [
"dev",
"us-south"
],
"last_update_date": "2020-12-15T22:34:53Z",
"name": "test-arbitrary-secret-in-group",
"secret_data": {
"payload": "secret-data"
},
"secret_group_id": "339c026a-ac0f-1ea1-3d43-99adf871b49a",
"secret_type": "arbitrary",
"state": 1,
"state_description": "Active",
"versions": [
{
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-15T22:34:53Z",
"id": "a7f55e6f-b068-977b-062e-4de644633982"
}
]
},
"wrap_info": null,
"warnings": null,
"auth": null
}
"request_id": "d8eb84fd-c0bd-08ae-c3ad-cff87606953c",
"lease_id": "",
"renewable": false,
"lease_duration": 0,
"data": {
"secrets": [
{
"created_by": "iam-ServiceId-c0c7cfa4-b24e-4917-ad74-278f2fee5ba0",
"creation_date": "2020-12-15T22:34:53Z",
"crn": "crn:v1:bluemix:public:secrets-manager:us-south:a/a5ebf2570dcaedf18d7ed78e216c263a:0f4c764e-dc3d-44d1-bd60-a2f7cd91e0c0:secret:a6972127-35ad-b36f-aac8-0223f0475cb6",
"description": "Extended description for my secret.",
"expiration_date": "2030-04-01T09:30:00Z",
"id": "a6972127-35ad-b36f-aac8-0223f0475cb6",
"labels":
"dev",
"us-south"
],
"last_update_date": "2020-12-15T22:34:53Z",
"name": "test-arbitrary-secret-in-group",
"secret_group_id": "339c026a-ac0f-1ea1-3d43-99adf871b49a",
"secret_type": "arbitrary",
"state": 1,
"state_description": "Active"
},
{
The name for the anonymous user. For example: "Anonymous":
name: "Anonymous"
 The public keystore will not be used with this setup.
 Specify an arbitrary 128-bit UUID below, e.g.:
tokenspaceID: "12345678-1234-1234-1234-1234567890AB"
iamauth:
<<: defaultiamcredential
 Provide the API key for the Anonymous user.
apikey: "<anonymous_user_api_key>"
logging:
 Set the logging level.
 The supported levels, in an increasing order of verboseness: 'panic', 'fatal', 'error', 'warning'/'warn', 'info', 'debug', 'trace'. The Default value is 'warning'.
loglevel: "info"
logpath: "/tmp/grep11client.log" The full path of your logging file.
Show more





 3. Install the Hyper Protect Crypto Services PKCS 11 library 



1.

[Download the latest PKCS #11 library](https://github.com/IBM-Cloud/hpcs-pkcs11/releases).
2. Copy the previously created configuration file grep11client.yaml and the PKCS #11 library pkcs11-grep11-<platform>.so.<version> into your Db2 container.
3. Run the following commands as root to install the Hyper Protect Crypto Services PKCS #11 library in your Db2 setup.

mkdir /etc/ep11client
chmod a+rx /etc/ep11client/
cp grep11client.yaml /etc/ep11client/grep11client.yaml
chmod a+r /etc/ep11client/grep11client.yaml

mkdir -p /pkcs11
cp pkcs11-grep11-<platform>.so.<version> /pkcs11/pkcs11-grep11.so