Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(api): allow token authentication for get_sound and list_sounds #18

Conversation

richard-kramer
Copy link
Contributor

Enables token authentication for the routes get_sound and list_sounds to allow accessing these via API call and e.g. directly use the soundfiles in an external application.

Fixes #17

@richard-kramer richard-kramer changed the title feat(api): allow token authentication for get_sound and `list_sound… feat(api): allow token authentication for get_sound and list_sounds Dec 29, 2023
@richard-kramer richard-kramer force-pushed the 20231229_17_kramer_allow-token-access-to-sounds branch from 31c3ed8 to fd29ee9 Compare December 29, 2023 09:12
@dominikks dominikks changed the base branch from main to development January 3, 2024 19:22
@dominikks
Copy link
Owner

Sure, I see no problem with that. Extending the permissions of the API token makes it a bit more worthwhile to look into securing it better (i.e., only allowing it to be downloaded once when it is created and allowing proper management of multiple keys), but that is an issue for another time. 😅

@dominikks dominikks merged commit e1ef165 into dominikks:development Jan 3, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Make individual sounds accessible via API+token
2 participants