The only way to authenticate with Serval is to use M2M access tokens from Auth0. Unfortunately, our current plan limits the number of M2M tokens that can be generated in a month. When we had out access keys to someone for testing or development, they can unknowingly use up all of the tokens. For these kinds of one-off testing clients, we should setup an alternative authentication scheme. The simplest approach would be to provide these users with an API key. Because they are long-lived, we would need a way to revoke the keys and issue a new one without the user losing access to all of their existing data.
The only way to authenticate with Serval is to use M2M access tokens from Auth0. Unfortunately, our current plan limits the number of M2M tokens that can be generated in a month. When we had out access keys to someone for testing or development, they can unknowingly use up all of the tokens. For these kinds of one-off testing clients, we should setup an alternative authentication scheme. The simplest approach would be to provide these users with an API key. Because they are long-lived, we would need a way to revoke the keys and issue a new one without the user losing access to all of their existing data.