Unknown macro: {next_previous_link3}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Description

You will have many certificates used for mutual SSL. In a situation where you wish to view all the certificate details, it is not feasible to show all the details on one page therefore the details are paginated.

Resource Path/paginate
URL/mdm-admin/certificates/paginate?start={start}&length={length}
HTTP MethodGET
Request/Response Formatapplication/json
cURL command
curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer <EMM_API_TOKEN>" -k -v https://<EMM_HOST>:<EMM_HTTPS_PORT>/mdm-admin/certificates/paginate?start={start}&length={length}
  • For more information on how to generate the <EMM_API_TOKEN>, see Generating the OAuth 2.0 Access Token.
  • By default, <EMM_HOST> is localhost. However, if you are using a public IP, the respective IP address or domain needs to be specified.
  • By default, <EMM_HTTPS_PORT> has been set to 9443. However, if the port offset has been incremented by n, the default port value needs to be incremented by n.
  • Provide the starting pagination index as the value for {start}. Example 1

     You will have many devices registered with the EMM. In a situation where you wish to view the all the registered devices it is not feasible to show all the details on one page therefore the details are paginated.
  • Provide how many certificate details you require from the starting pagination index as the value for {length}. For example if you require the device details from the 1st pagination index to the 2nd, you must define 1 as the value for start and 2 as the value for length.

    If you wish to get the device details within a predefined index range, you need to define both the start and length fields.
    Example:  https://localhost:9443/mdm-admin/devices?start=10&length=5 There will be situations were you will not have device details in the specified index range. In such situation all the details of the devices registered to EMM will be given.

Example:

curl -X GET -H "Content-Type: application/json" -H "Authorization: Bearer f4c0c1b2b4ace7040132682139d51f74" -k -v https://localhost:9443/mdm-admin/certificates/paginate?start=1&length=2
 Sample output
 

The = sign will be given as the encoded, which is \u003d. This needs to be escaped.

Sample JSON output
Definition 
 {
  "recordsTotal": 2,
  "data": [
    {
      "serialNumber": "124380353155528759302",
      "tenantId": -1234,
      "notAfter": 1487051941000,
      "notBefore": 1455515941000,
      "certificateserial": 12438035315552875939,
      "issuer": "CN=10.10.10.24, OU=sa, O=as, L=asd, ST=asd, C=sl",
      "subject": "CN=10.10.10.24, OU=sa, O=as, L=asd, ST=asd, C=sl",
      "certificateVersion": 3
    },
    {
      "serialNumber": "12438035315552875930",
      "tenantId": -1234,
      "notAfter": 1487051941000,
      "notBefore": 1455515941000,
      "certificateserial": 12438035315552875939,
      "issuer": "CN=10.10.10.24, OU=sa, O=as, L=asd, ST=asd, C=sl",
      "subject": "CN=10.10.10.24, OU=sa, O=as, L=asd, ST=asd, C=sl",
      "certificateVersion": 3
    }
  ]
}

Property Value

Description

Data
Type 
recordsTotalThe number of records that are given.String
dataThe data that will be givenString
serial

It is the unique ID to identify a certificate. In device enrollment this is the common name of the client's certificate.

String
tenantIdThe ID of the tenant that added the certificate.String
notAfter String
notBefore String

certificateserial

 String

issuer

 String

subject

 String

certificateVersion

The version of the SSL certificate.String
  • No labels