![]() ![]() So you are responsible for the keys, but if you take reasonable precautions to prevent misuse (such as not making displaying them to the user, or making them available outside of your app), and your app isn’t designed with malicious intent, then it is unlikely Twitch would take action against you (please keep in mind I’m not a legal expert, nor do I speak for Twitch). Also, you may not sell, transfer, or sub-license them. All activities that occur using your Keys are your responsibility. ![]() The Keys enable us to associate the Program Materials with Your Services and end users of Twitch Services. ![]() Once you have successfully registered Your Services, you will be issued one or more unique security keys, secrets, tokens, access codes, passwords, or other credentials (collectively, “Keys”). The Twitch Developer Agreement states: IV. It’s also possible that someone could use a client-id to make requests without the use of a bearer token, and I was also wondering how exposing the client-id might potentially open that up as an attack vector for bad actors. I do not want my app to be banned because of one bad actor getting hold of a bearer token. responsibility based on client-id) or will the user making the abusive requests be held responsible (i.e. In case someone does abuse the API in this manner, will I, as the app author, be held responsible (i.e. Is the rate limit bound to bearer tokens when provided (or something similar), or is it global? If it’s global, it would mean that misuse could result in a DOS attack on my app. I have two questions regarding this potential issue: This would look like it’s my app doing it, even though it’s not. My concern with this is that someone with ill intentions could take these two codes and use them to spam or otherwise misuse the API. it has no online component), which means I’d be locally storing the client-id and the bearer token for any users the app is authorised to act on behalf of (after obtaining the latter using implicit code flow). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |