Untethered Mode

This mode configuration mode, all API configurations and their policies are managed through the V3 API layer.

In order to access the V3 APIs, first, create an access token using your specific credentials, such as: 4g4d3zaxnbvp9ee7kdnum8as:JTJCrVeW7d as shown in the examples below:

  1. Begin by creating an access token.
    curl -v -u 4g4d3zaxnbvp9ee7kdnum8as:JTJCrVeW7d -H 'Host: api.tml.mashspud.com' 'http://a981e26fd5b1f11e98d7b06eb89ed329-73173243.us-east-1.elb.amazonaws.com:7080/v3/token' -d "grant_type=password&username=localdevadmin&password=ch4ng3m3&scope=84e9d6f1-920d-4b6c-9289-5432c6fd39b7"
    
  2. Create an identity:
  3. Create a certificate:
  4. Create an HTTP Client Profile.
    Use the access token from the first call in the request header, e.g. "xhah3bv2acgnxjmtun7fwhh8" and associate the identity and the certificate to the https client profile.
    curl  -H 'Authorization: Bearer xhah3bv2acgnxjmtun7fwhh8' -H 'Content-Type: application/json' -H 'Host: api.tml.mashspud.com' 'http://a981e26fd5b1f11e98d7b06eb89ed329-73173243.us-east-1.elb.amazonaws.com:7080/v3/rest/httpsClientProfiles' -d '{"name":"TestHttpClientProfile", "description":"Test Description", "verifyHostname": false, "httpsClientTrusts":[{"id":"YOUR_TRUST_CERT_UUID"}], "identity":{"id":"YOUR_IDENTITY_UUID"}}'
     
    Response:
     
    {"created":"2019-04-18T20:54:22.745+0000","updated":"2019-04-18T20:54:22.745+0000","sni":false,"verifyHostname":false,"httpsClientTrusts":[{"created":"2019-04-18T20:54:22.745+0000","updated":"2019-04-18T20:54:22.745+0000","id":"5cdf6dba-322f-410a-b4e7-75083e87e752"}],"identity":{"serialNumber":"5c9a9404","created":"2019-04-03T23:53:59.000+0000","updated":"2019-04-03T23:53:59.000+0000","expiration":"2020-03-27T04:05:09.000+0000","fingerprint":"DB:13:C6:CF:79:79:C4:6F:29:AE:0B:7E:3D:89:A2:5F","name":"TestHttpClientProfile","id":"0f825c1c-b01e-41b2-80f1-6d6bdc4b39d1"},"description":"Test Description","name":"TestHttpClientProfileFromCall","id":"2415970a-fc85-4029-acab-9a349334838f"}
    
  5. The HTTPS Client Profile can now be associated with the identity and/or certificate.