Management
In order for a T1C-API to be downloadable from and be able to register with the Distribution Service, a few steps must be executed.
Management User Interface
In development
REST API
We offer a Postman collection of the DS REST API which you can use. Below we will provide more information on the endpoints and their parameters.
Obtain IDP Token
For the management endpoints a user JSON web token is necessary. it can be obtained from the IDP and must be included in all management requests to the DS REST API as a bearer token
Example
Request
Note that the request is x-www-form-urlencoded
The response will contain an access_token
property value which can be used in management requests made to the DS REST API.
Sample response
Create Or Update Version
It is necessary to create a version in order to have a valid registration API key for the installer packages
Example
Request
Create Or Update Context Config
The context config contains variable configuration for the installed T1C-API packages
Example
Wildcards in the CORS allowlist are only supported from the T1C API/Proxy v3.2.6 onwards.
Request
Create Or Update File Digests Config
The file digests config contains a list of files and their MD5 digests. At startup, the T1C-API will verify that these files are unaltered and shut down if that is not the case. We recommend leaving it empty during testing.
Example
Request
Create or Update SSL Keystore Config
The SSL keystore config contains the URI for the latest SSL keystore used by the T1C-API for it's local server. The T1C-API will check if it has the latest and unaltered SSL keystore at startup and replace it if necessary.
Example
Request
Create Or Update Organization
An organization is an entity that groups labels together. It is required in order to create a label
Example
Request
Create Or Update Label
A label is analogous to an application in the DS API v2. In v3 a label is associated with an API key which applications can exchange for a temporary JSON web token that can be passed to the client. A label can be used by multiple applications, or a label can be created for each application.
Example
Request
Label IDs must be unique across all organizations as the T1C-API is not aware of any organizational context, only labels.
Update CORS Configuration
Starting from v3.5.x, the CORS is configured centrally regardless of version and is enabled by default. If no allowed origins are configured or the centrally configured CORS filter is disabled, the old flow is used and the versioned context config will be used to update the T1C installations.
Example
Request
Create Allowed Origin
Add an origin to the allowed origins list. Wildcards can be used if enabled in the general configuration.
Example
Request
Update Allowed Origin
Update an allowed origin.
Example
Request
Update Multiple CORS Allowed Origins
Update multiple allowed origins. If you provide an unknown/self-generated ID with a non-existing origin, the DS will create it instead. This method can be used to create multiple allowed origins in 1 request.
Example
Request
Delete CORS Allowed Origin
Delete an allowed origin.
Example
Create CORS Exposed Header
Create a custom HTTP header to be exposed in the response (by default no headers are exposed)
Example
Request
Update CORS Exposed Header
Update a custom HTTP headers to be exposed in the response
Example
Request
Update Multiple CORS Exposed Headers
Update multiple custom HTTP headers to be exposed in the response. If you provide an unknown/self-generated ID with a non-existing header name, the DS will create it instead. This method can be used to create multiple exposed headers. in 1 request.
Example
Request
Delete CORS Exposed Header
Delete a custom HTTP headers to be exposed in the response
Example
Last updated