Currently the OAuth-Twitch link has to be build by hand and its is never checked if the environment variables have been set
Example:
https://id.twitch.tv/oauth2/authorize?response_type=code&client_id=<CLIENT_ID>&scope=channel:moderate+chat:edit+chat:read+moderator:manage:banned_users&redirect_uri=http://localhost/auth_callback
CLIENT_ID
Is known at runtime.
static final String APP_CLIENT_ID = System.getenv("APP_ID");
Scopes
Could be put together on the fly depending on the needs of the User's Kindle to timeout / ban etc. user
Example:
scope=channel:moderate+chat:edit+chat:read+moderator:manage:banned_users
Could be in future be put together on the fly depending if the user's Kindle needs to timeout / ban etc. user
callback
Callback is known at compile time.
Example:
redirect_uri=http://localhost/auth_callback
Currently the OAuth-Twitch link has to be build by hand and its is never checked if the environment variables have been set Example:
https://id.twitch.tv/oauth2/authorize?response_type=code&client_id=<CLIENT_ID>&scope=channel:moderate+chat:edit+chat:read+moderator:manage:banned_users&redirect_uri=http://localhost/auth_callbackstatic final String APP_CLIENT_ID = System.getenv("APP_ID");Scopes Could be put together on the fly depending on the needs of the User's Kindle to timeout / ban etc. user Example:
scope=channel:moderate+chat:edit+chat:read+moderator:manage:banned_usersCould be in future be put together on the fly depending if the user's Kindle needs to timeout / ban etc. usercallback Callback is known at compile time. Example:
redirect_uri=http://localhost/auth_callbackAvailable scopes: Documentation