Cloud and Enterprise Only
Application packages specify state machines running both on the end device and the Application Server, as well as signalling messages exchanged between the end device’s application layer and the Application Server.
The Things Stack binary can be configured with many different options. Those options can be provided as command-line flags, environment variables or using a configuration file.
The streaming data integrations provide multiple formats for the delivery of application uplink messages and downlink queue operations. This section will delve into the common formats used by them.
Email templates define the contents of the emails that The Things Stack sends to its users. They allow network operators to override the default contents of the emails with their own custom contents.
Federated Authentication New in 3.10
Federated Authentication allows network administrators to use the already existing identity providers in order to authenticate users, instead of manually creating and managing the accounts in The Things Stack.
This reference contains common terms and definitions to help you find your way around The Things Stack.
The Things Stack expects the root of interoperability repository to contain
config.yml, which contains various interoperablity configuration options.
The Things Stack uses a port per protocol, with a TLS counterpart when applicable. Ports can be shared by multiple services using the same protocol, i.e. gRPC services sharing management, data and events services.
This section contains links to common root SSL certificates used in The Things Stack, issued by trusted certificate authorities (CAs).