The Identity device grant flow is implemented in the DeviceAuth class. The flow is entirely between your server and Twitch’s Identity server. Since it does not involve a user, it does not involve a Web browser. This flow is intended only for servers since it requires your client secret. The OAuth client credentials grant flow is implemented in the ApplicationAuth class. In this case, the redirect URI registered for your application must use a custom, non-standard scheme (not one of the standard schemes) to prevent the browser from interpreting it incorrectly and to allow the Authorization SDK to capture it. Users will need the platform’s Web browser to complete the flow. To use this flow, you do not need a Web server, since the token is passed as part of the redirect URI. The OAuth implicit flow is implemented in the ClientAuth class. The redirect URI registered for your application will be for your Web server. The user will use the platform’s Web browser to complete the flow. To use this flow, you need a Web server to handle the token exchange with Twitch. The OAuth grant flow is implemented in the ServerAuth class. The Authorization SDK has four forms of authorization: three based on directly on OAuth and a third that also provides an OAuth token: ![]() To configure your application for use with Twitch Authorization, refer to the Twitch Authentication Guide. There are several library files, both static and dynamic, for these platforms in both debug and release builds. Most of the classes and methods are similar between the two versions, so familiarity with one will help you learn the other.
0 Comments
Leave a Reply. |