- URL:
- https://<root>/security/sslCertificates/<sslCertificate>
- Methods:
GET- Version Introduced:
- 10.3
Access requirements
Required privileges
The Portal 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 Portal 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 generate operation in the Portal Directory API. For security reasons, all POST requests made to the Portal Administrator API must include a token in the request body.
Description
The resource for an individual SSL certificate returns the certificate's details.
Request parameters
| Parameter | Details |
|---|---|
| The response format. The default response value is Values: |
Example usage
The following is a sample request URL used to access an individual SSL certificate resource:
https://organization.example.com/<context>/portaladmin/security/sslCertificates/myCert?f=pjsonJSON Response syntax
{
"aliasName": "<alias>",
"entryType": "PrivateKeyEntry",
"issuer": "<certificate issuer information>",
"subject": "<certificate subject information>",
"subjectAlternativeName": [<alternate name information>],
"validFrom": "<starting date and time information for certificate validity>",
"validUntil": "<ending date and time information for certificate validity>",
"validFromEpoch": "<Epoch format of the of starting date above>", //Introduced at ArcGIS Enterprise 11.1
"validUntilEpoch": "<Epoch format of the ending date above>", //Introduced at ArcGIS Enterprise 11.1
"keyAlgorithm": "<key algorithm>",
"keySize": "<key size>",
"serialNumber": "<serial number>",
"version": "3",
"signatureAlgorithm": "<signature algorithm>",
"keyUsage": [<key usage>],
"md5Fingerprint": "<MD5 fingerprint>",
"sha1Fingerprint": "<SHA1 fingerprint>",
"sha256Fingerprint": "<SHA256 fingerprint>"
}JSON Response example
{
"aliasName": "selfsignedcertificate",
"entryType": "PrivateKeyEntry",
"issuer": "CN=SERVER.COMPANY.COM, O=SelfSignedCertificate",
"subject": "CN=SERVER.COMPANY.COM, O=SelfSignedCertificate",
"subjectAlternativeNames": ["DNSName: MACHINE.EXAMPLE.COM"],
"validFrom": "Fri Dec 16 06:07:04 PST 2022",
"validUntil": "Sun Oct 24 07:07:04 PDT 2055",
"validFromEpoch": 1671199624000,
"validUntilEpoch": 2707999624000,
"keyAlgorithm": "RSA",
"keySize": 2048,
"serialNumber": "64ed6d0f",
"version": 3,
"signatureAlgorithm": "SHA256withRSA",
"keyUsage": [],
"md5Fingerprint": "a1dbaf706d2befc43beaf9bfb9f639df",
"sha1Fingerprint": "980fbeaa248f624144ee87e192da473f6c8ea78f",
"sha256Fingerprint": "fef71dd8827b30b2b88032cc6f035a2a6aa810f2ce324cbecbb3fdeced0279d1"
}