# Live extension, Setting configuration now gets 401: Unauthorized

**URL:** <https://staging-discuss.dev.twitch.com/t/live-extension-setting-configuration-now-gets-401-unauthorized/13373>\
**Category:** Extensions\
**Created:** [December 20, 2017, 7:56pm UTC](https://staging-discuss.dev.twitch.com/t/live-extension-setting-configuration-now-gets-401-unauthorized/13373 "2017-12-20T19:56:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![willoughby](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/willoughby/32/3865_2.png) [@willoughby](https://staging-discuss.dev.twitch.com/u/willoughby)\
**Post date:** [December 20, 2017, 7:56pm UTC](https://staging-discuss.dev.twitch.com/t/live-extension-setting-configuration-now-gets-401-unauthorized/13373/1 "2017-12-20T19:56:03Z")

</div>

My extension went live this week, part of it requires the user to enter a url in the config page which once persisted calls the [https://api.twitch.tv/extensions/{extension\_id}/0.0.1/required\_configuration?channel\_id=](https://api.twitch.tv/extensions/%7Bextension_id%7D/0.0.1/required_configuration?channel_id=) endpoint to allow activation.

During development the extension was allowed to be activated, now that its live I get the following response from the endpoint:

{  
“error”: “Unauthorized”,  
“status”: 401,  
“message”: “{\n “status”: 401,\n “message”: “Sorry, you’re not allowed to do that”,\n “error”: “Unauthorized”\n}”  
}

Code on the server hasn’t changed as its using a lambda function. Im pretty much at a lose as to what the problem could be.

---

<div class="post-metadata">

**Author:** ![BarryCarlyon](https://d1d6mrmdu7ztse.cloudfront.net/user_avatar/staging-discuss.dev.twitch.com/barrycarlyon/32/253_2.png) [@BarryCarlyon](https://staging-discuss.dev.twitch.com/u/BarryCarlyon)\
**Post date:** [December 21, 2017, 10:42am UTC](https://staging-discuss.dev.twitch.com/t/live-extension-setting-configuration-now-gets-401-unauthorized/13373/2 "2017-12-21T10:42:32Z")

</div>

Sounds like you have the wrong or no clientID or extension secret loaded into lambda?