---
title: EnvironmentAndSystemPropertySecretsStore
description: Resource path:
component: pingam
version: 8.1
page_id: pingam:entity-reference:sec-amster-entity-environmentandsystempropertysecretsstore
canonical_url: https://docs.pingidentity.com/pingam/8.1/entity-reference/sec-amster-entity-environmentandsystempropertysecretsstore.html
section_ids:
  sec-amster-entity-environmentandsystempropertysecretsstore-global-ops: Global Operations
  sec-amster-entity-environmentandsystempropertysecretsstore-global-ops-getalltypes: getAllTypes
  sec-amster-entity-environmentandsystempropertysecretsstore-global-ops-getcreatabletypes: getCreatableTypes
  sec-amster-entity-environmentandsystempropertysecretsstore-global-ops-nextdescendents: nextdescendents
  sec-amster-entity-environmentandsystempropertysecretsstore-global-ops-read: read
  sec-amster-entity-environmentandsystempropertysecretsstore-global-ops-update: update
---

# EnvironmentAndSystemPropertySecretsStore

## Global Operations

Resource path:

```
/global-config/secrets/stores/EnvironmentAndSystemPropertySecretStore
```

Resource version: `1.0`

### getAllTypes

Obtain the collection of all secondary configuration types related to the resource.

**Usage**

```
am> action EnvironmentAndSystemPropertySecretsStore --global --actionName getAllTypes
```

### getCreatableTypes

Obtain the collection of secondary configuration types that have yet to be added to the resource.

**Usage**

```
am> action EnvironmentAndSystemPropertySecretsStore --global --actionName getCreatableTypes
```

### nextdescendents

Obtain the collection of secondary configuration instances that have been added to the resource.

**Usage**

```
am> action EnvironmentAndSystemPropertySecretsStore --global --actionName nextdescendents
```

### read

**Usage**

```
am> read EnvironmentAndSystemPropertySecretsStore --global
```

### update

**Usage**

```
am> update EnvironmentAndSystemPropertySecretsStore --global --body body
```

**Parameters**

* *\--body*

  The resource in JSON format, described by the following JSON schema:

  ```json
  {
    "type" : "object",
    "properties" : {
      "format" : {
        "title" : "Value format",
        "description" : "Indicates what format is used to store the secrets in the files. The available options are: <ul> <li>Plain text: the secrets are stored as UTF-8 encoded text.</li> <li>Base64 encoded: the secrets are stored as Base64 encoded binary values.</li> <li>Encrypted text: the plain text secrets are encrypted using AM's encryption key.</li> <li>Encrypted Base64 encoded: the Base64 encoded binary values are encrypted using AM's encryption key.</li>  <li>Encrypted with Google KMS: the secrets are encrypted using Google's Key Management Service.</li> <li>PEM encoded certificate or key: the secrets are certificates, keys, or passwords, in Privacy Enhanced Mail (PEM) format, such as those produced by OpenSSL and other common tools.</li> <li>Encrypted PEM: PEM-encoded objects that are encrypted with AM's server key.</li><li>Google KMS-encrypted PEM: PEM-encoded objects that are encrypted with Google KMS.</li></ul><p>The following formats are also supported but are discouraged (use the PEM variants instead): <ul><li>Encrypted HMAC key: the Base64 encoded binary representation of the HMAC key is encrypted using AM's encryption key. Use this format when working with non generic secrets.</li> <li>Base64 encoded HMAC key: the secrets are binary HMAC keys encoded with Base64.</li> <li>Google KMS-encrypted HMAC key: the secrets are binary HMAC keys that have been encrypted with Google's Key Management Service (KMS).</li> </ul>",
        "propertyOrder" : 100,
        "required" : true,
        "type" : "string",
        "exampleValue" : ""
      }
    }
  }
  ```