HRN of the identity to whom to also grant read access. For a secure production system using Application delegates, this is a convenience API that can be used to create a Secret and grant read access in one step. When used with a delegate App and the RunAsId feature, the target App's background runtimes will receive the decoded secret in a file.

You can also omit this parameter, and optionally invoke the Grants API at a later time, to achieve the same effect.

ID for the Secret. ID must contain 4 and 16 lowercase alphanumeric characters [a-z0-9] plus the hyphen character [-].

Web-safe-base64-encoded secret file contents. This property is redacted from the Retrieve Secret and List Secrets APIs, but is securely delivered to Platform Runtimes, as long as the Secret is enabled and not expired. The 'sha256' property in the Retrieve Secret and List Secrets APIs response provides the ability to validate the stored value, but since sha-256 is a one-way hash, the underlying 'secret' remains hidden from view.

"aws" or "custom". For "aws", the platform will place the file in ~/.aws/. For "custom", the platform will place the file in ~/.here/.

A relative filename for the platform to use to write the secret in plaintext on the filesystem. The file will be placed in the directory as specified by the 'type' property. Defaults to "credentials".

a descriptive name for the secret

Date-time formatted time this Secret expires. A null value or missing property means there is no end time at which the secret expires. This property has no effect if enabled=false. An expired secret is not delivered to Platform Runtimes.

Correlates HTTP requests between a client and server. If not present in the incoming request, it will be generated. This header and value will be included in all loglines including access logs. It will also be propagated to downstream services and returned in the response.

The unique for the request, used to track this request within the service. X-Request-ID value is NOT propagated to the downstream services.