Tempo Client Credentials Grant?

[Jared Czeizinger]

Does Tempo lack any form of Oauth 2.0 2LO/Client Credentials grant for building automations?

The only options I can find are Oauth 2.0 3LO connections, which force me to write exhaustive documentation solely for reapproving the connection in case of an incident, or an "API Integration" which forces me to physically implement a new token at set intervals.

Neither of these is an acceptable option for building machine-to-machine automations. Am I missing something here?

[Arkadiusz Wroblewski]

Hello and welcome to the Community @Jared Czeizinger 

from what Tempo currently documents, I do not see a supported OAuth 2.0 client credentials / 2LO flow for Tempo Cloud.

The documented options are:

- OAuth 2.0 Applications

- API Integration user tokens

So for a true machine-to-machine setup, your conclusion looks right. There is no native client credentials grant available.

If this is a blocker or you have specific security/compliance requirements, I would recommend reaching out directly to Tempo support, as they can confirm the current state and any or alternatives.