T1C-Proxyand only exposes the following use cases:
T1C-Proxyoperates by Default on the API port defined in the
T1C-DS(Distribution Server). From a Web Application perspective, this is the only information known. When a Web Application requests the information of the device, the PROXY device type will inform the Web Application that the targeted underlying API is a PROXY, which means that the Web Application must ask for the Agent specific API port to configure an URI which can be used to execute the use cases.
T1C-SDK-JSthis is done implicitly during initialisation.
T1C-APIinstalled for a specific users runs in [User Space]. To avoid possible attack vectors, the Trust1Connector v3 will always run in [User Space].
T1C-API, during the post install phase, the
T1C-APIwill try to verify automatically if it is running in a shared environment. If this is the case, the
T1C-APIwill ask the T1C-Proxy for available ports and will reserve those post, prior to initialisation and startup.
T1C-Proxyare the following:
T1C-APIPort: This is the port exposing the OpenAPI interface towards Web Applications and used by the
RESERVEDin the Agent Registry of the
T1C-Proxy. Upon T1C-API initialisation, the port configurations will be confirmed and the Agent Registry will set the device state on
REGISTERED. From this moment on, a T1C-API instance, running in an active user session, will be available for the Web Application via the consent flow.
T1C-gRPCinstance is inherently a component from the
T1C-API, and thus is managed by the
T1C-API. As each user must have it's own hardened runtime for communication purpose, the port assigned for
T1C-gRPCwill be registered and configured by the
T1C-API(and restarted when needed).