Starting from Secure Transport 5.2.x versions this information can be obtained through the Administrator's RESTful API. The main task while maintaining the Secure Transport server and account certificates is to identify the expiration time of each certificate. The existing 'ckcerts' in the $FILEDRIVEHOME/bin folder provides information limited to the local server certificates and the internal CA. Maintaining these certificates by knowing which certificate expires when, can become a challenging task over time. They are used for various purposes - authentication, encryption, decryption, certificate validation, etc. Validation is done on the server side.Secure Transports stores different public and private certificates and keys. Representations are annotated according to JSR 303. In addition to them, Java programs require the jackson libraries version 1.9.2 and validation-api version 1.0.0 GA from J2EE 6. The ws-representation library depends on the jersey-core and jersey-server-linking libraries version 1.13 which are available from. With API 2.0, in order to use REST API with Java, generate the Swagger client stubs from swagger.yaml file.įor Java use of the REST API, the SecureTransport Java API provides a library called ws-representation, which includes Java classes that represent the data that can be accessed using the REST API. The following information is valid only for API versions prior to 2.0. API 2.0 does not support application/xml media data type. The Internet media data types supported by the REST API versions prior to 2.0 are application/json and application/xml. These methods and the provided resources allow access to a single element or a collection of elements.
For more information about SecureTransport API 2.0, refer to its Swagger documentation.
API 2.0 also supports the PATCH and HEAD methods.
The versions of the SecureTransport API before 2.0 support the following HTTP methods: GET, PUT, POST, and DELETE.