feat: add support for token-based authentication #116
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
This PR adds proper support for temporary token authentication to the Deepgram Rust SDK. I'm working on a client-side application, and I was surprised to discover that the SDK only supported API key authentication with the "Token" prefix, thus not supporting token-based auth.
Token
prefix (e.g.,Token dg_xxx
)Bearer
prefix (e.g.,Bearer dg_xxx
)The existing implementation incorrectly used "Token" for all authentication, which worked for API keys but was wrong for temporary tokens.
Changes:
There are no breaking changes to current apps.
AuthMethod
enum to distinguish between API keys and temporary tokensDeepgram
struct to use the new authentication system (by default it'll still use API keys)Deepgram::with_temp_token()
constructor for temporary token authenticationAll existing tests pass, and the change is backwards compatible for API usage patterns.
Types of changes
Checklist