# Replacement for chat\_login scope?

**URL:** <https://discuss.dev.twitch.com/t/replacement-for-chat-login-scope/24237>\
**Category:** Chat and IRC\
**Created:** [February 24, 2020, 5:51pm UTC](https://discuss.dev.twitch.com/t/replacement-for-chat-login-scope/24237 "2020-02-24T17:51:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![pekef58177](https://avatars.discourse-cdn.com/v4/letter/p/3ab097/32.png) [@pekef58177](https://discuss.dev.twitch.com/u/pekef58177)\
**Post date:** [February 24, 2020, 5:51pm UTC](https://discuss.dev.twitch.com/t/replacement-for-chat-login-scope/24237/1 "2020-02-24T17:51:06Z")

</div>

i see in the docs that chat\_login scope is deprecated and cannot be used for new clients. what is the right way to authenticate to chat for something like irc addon for the kodi media center? testing with an existing oauth token for chat seems to result in ‘Login Failed’ errors.

i searched on here for chat\_login but didn’t find anything recent or helpful.

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [February 24, 2020, 5:51pm UTC](https://discuss.dev.twitch.com/t/replacement-for-chat-login-scope/24237/2 "2020-02-24T17:51:48Z")

</div>

> **[Authentication](https://dev.twitch.tv/docs/authentication/#scopes)**
>
> Authentication

Scroll to the bottom for “Chat and PubSub”

---

<div class="post-metadata">

**Author:** ![pekef58177](https://avatars.discourse-cdn.com/v4/letter/p/3ab097/32.png) [@pekef58177](https://discuss.dev.twitch.com/u/pekef58177)\
**Post date:** [February 24, 2020, 6:33pm UTC](https://discuss.dev.twitch.com/t/replacement-for-chat-login-scope/24237/3 "2020-02-24T18:33:23Z")

</div>

what is the right site i can use to generate tokens with the right scopes for this or if i wanted a separate chat bot for my channel? i saw one before but not sure if its using the deprecated scope.

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [February 24, 2020, 6:34pm UTC](https://discuss.dev.twitch.com/t/replacement-for-chat-login-scope/24237/4 "2020-02-24T18:34:37Z")

</div>

You should create your _own_ oAuth Server/management and not rely on someone else for this

---

<div class="post-metadata">

**Author:** ![pekef58177](https://avatars.discourse-cdn.com/v4/letter/p/3ab097/32.png) [@pekef58177](https://discuss.dev.twitch.com/u/pekef58177)\
**Post date:** [February 24, 2020, 7:10pm UTC](https://discuss.dev.twitch.com/t/replacement-for-chat-login-scope/24237/5 "2020-02-24T19:10:59Z")

</div>

that is fair, was just curious since in the past there was something you could use for these tokens to easily add to bots. instead of writing the whole server yourself.

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d3ovvz0v2ajtpu.cloudfront.net/user_avatar/discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [February 24, 2020, 7:12pm UTC](https://discuss.dev.twitch.com/t/replacement-for-chat-login-scope/24237/6 "2020-02-24T19:12:18Z")

</div>

My bots use my own oAuth flow.

So that if someone elses system breaks then I’m not affected.  
And allows me to refresh my own tokens.

Generally speaking a user token lasts for four hours, but you only need to refresh at connection to chat.

---

<div class="post-metadata">

**Author:** ![system](https://d2opxh93rbxzdn.cloudfront.net/original/2X/0/05909729875cce3b53e59d5561c4d23bb14948fc.png) [@system](https://discuss.dev.twitch.com/u/system)\
**Post date:** [March 25, 2020, 7:12pm UTC](https://discuss.dev.twitch.com/t/replacement-for-chat-login-scope/24237/7 "2020-03-25T19:12:19Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
