Skip to content
URL:
https://<root>/security/certificates/trust
Methods:
GET
Operations:
Import
Child Resources:
Certificate
Version Introduced:
10.9

Access requirements

Required privileges

The Enterprise Administrator API requires privilege-based access. An administrator must be assigned a specific user privilege, or role, to access any given endpoint. Listed below are the user privileges or roles an administrator can be assigned that provides access to this endpoint. If multiple privileges are listed, only one needs to be assigned to gain access.


Tokens

This API requires token-based authentication. A token is automatically generated for administrators who sign in to the Enterprise Administrator API directory's HTML interface. Tokens generated in this way are stored for the entirety of the session.

Those accessing the API directory outside of the HTML interface will need to acquire a session token from the generateToken operation in the Enterprise Directory API. For security reasons, all POST requests made to the Enterprise Administrator API must include a token in the request body.


Learn how to generate a token

Description

The trust resource lists all the configured trust certificates for an organization. This resource also provides access to child resources and operations that can be used to manage trust certificates.

Request parameters

ParameterDetails

f

The response format. The default format is html.

Values: html | json | pjson

Example usage

The following is a sample request URL used to access the trust resource:

Use dark colors for code blocksCopy
1
https://organization.example.com/<context>/admin/security/certificates/trust?f=pjson

JSON Response example

Use dark colors for code blocksCopy
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
{
  "certificates": [
    {
      "validUntilAsEpoch": 1669240636000,
      "keyAlgorithm": "RSA",
      "serialNumber": "4f00002139a2fc7fccba8d6d16000000002139",
      "keySize": 2048,
      "subject": "CN=*.demo-gis.com, OU=Dev, O=Esri, L=Redlands, ST=California, C=US",
      "subjectAlternativeNames": ["DNSName: *.demo-gis.com"],
      "sha1Fingerprint": "544c68e0e3852196fc24afc8355dd1088d3cc3ec",
      "validFrom": "Mon Nov 23 21:57:16 UTC 2020",
      "type": "TRUST",
      "version": 3,
      "md5Fingerprint": "c0dea2ef34fbc74c2c0ce910bedc6d5a",
      "issuer": "CN=Esri Issuing CA, DC=esri, DC=com",
      "signatureAlgorithm": "SHA256withRSA",
      "keyUsage": [
        "Digital_Signature",
        "Key_Encipherment"
      ],
      "name": "eks",
      "sha256Fingerprint": "004352446b12b9636e77d6107341671deb9bf7209836e8a855c933ccab06cd31",
      "validUntil": "Wed Nov 23 21:57:16 UTC 2022",
      "id": "cm7cxbfjehs8cn69zs72e",
      "validFromAsEpoch": 1606168636000
    }
  ]
}

Your browser is no longer supported. Please upgrade your browser for the best experience. See our browser deprecation post for more details.