Bug 23199

Summary: Minitube fails with "403 forbidden" errors for any operation
Product: Mageia Reporter: JanKusanagi <jan-bugs>
Component: RPM PackagesAssignee: QA Team <qa-bugs>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: cooker, jan-bugs, marja11, sysadmin-bugs, tmb
Version: 6Keywords: advisory, validated_update
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard: MGA6-64-OK
Source RPM: minitube-2.9-1.mga7.src.rpm CVE:
Status comment:

Description JanKusanagi 2018-06-18 18:34:33 CEST 
Description of problem:

Starting today, Minitube can no longer play anything, be it the result of a search, or one of the subscribed channels.

All API calls seem to fail with "403 Forbidden" errors.

Launching a search for "test" prints this to the console:
[unknown] CachedHttp MISS "https://www.googleapis.com/youtube/v3/search?key=*****&part=snippet&type=video&maxResults=50&q=test&safeSearch=none"
[unknown] Http: "https://www.googleapis.com/youtube/v3/search?key=*****&part=snippet&type=video&maxResults=50&q=test&safeSearch=none 403 Forbidden"

(I removed the API key just in case).

If I use that URL with CURL, I get this JSON error:

{
 "error": {
  "errors": [
   {
    "domain": "usageLimits",
    "reason": "accessNotConfigured",
    "message": "Access Not Configured. YouTube Data API has not been used in project 1039996407057 before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=*** then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.",
    "extendedHelp": "https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=***"
   }
  ],
  "code": 403,
  "message": "Access Not Configured. YouTube Data API has not been used in project *** before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/youtube.googleapis.com/overview?project=*** then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry."
 }
}

Again, censoring project number just in case.

The message suggests there's something to be done regarding the account used to generate the API key that Mageia's Minitube uses, not rebuilding or anything.



Version-Release number of selected component (if applicable):

Version     : 2.9
Release     : 1.mga7


How reproducible:

Always.


Steps to Reproduce:
1. Launch Minitube, preferably from a terminal window.
2. Enter anything in the search field, press enter
3. URL that failed is shown as error message in the results pane.



Thanks!
Comment 1 JanKusanagi 2018-06-18 18:35:03 CEST 
Forgot to add: users of Mageia 6 are affected too.
Jani Välimaa 2018-06-18 19:36:05 CEST

CC: (none) => cooker

Comment 2 Marja Van Waes 2018-06-18 20:34:05 CEST 
Assigning to the registered minitube maintainer.

CC: (none) => marja11
Assignee: bugsquad => jani.valimaa

Marja Van Waes 2018-06-18 20:34:35 CEST

Whiteboard: (none) => MGA6TOO

Comment 3 Johnny A. Solbu 2018-06-18 20:50:05 CEST 
The API key is owned by Mageia, so Mageia need to re-enable the key or generate a new one for minitube to use.
Comment 4 Jani Välimaa 2018-06-19 15:48:44 CEST 
(In reply to Johnny A. Solbu from comment #3)
> The API key is owned by Mageia, so Mageia need to re-enable the key or
> generate a new one for minitube to use.

Who has access to that key? Where did it came from?
Comment 5 Johnny A. Solbu 2018-06-19 18:45:25 CEST 
(In reply to Jani Välimaa from comment #4)
> (In reply to Johnny A. Solbu from comment #3)
> > The API key is owned by Mageia, so Mageia need to re-enable the key or
> > generate a new one for minitube to use.
> 
> Who has access to that key? Where did it came from?

Browsing my dev list archive, I see I was adviced to use the chromium-browser-stable api key, which have since been changed.

I'll change the key used in minitube, and add a note in the chromium spec to also change the key in minitube when the api key changes.
Comment 6 Johnny A. Solbu 2018-06-19 18:48:35 CEST 
(In reply to Johnny A. Solbu from comment #5)
> Browsing my dev list archive, I see I was adviced to use the
> chromium-browser-stable api key, which have since been changed.

Or not. I just checked, and chromium-browser-stable uses the same key.
Which means the browser should start to have access issues too.
Comment 7 Johnny A. Solbu 2018-06-20 13:46:53 CEST 
New package submitted to cauldron.
update for mga6 is comming.
Comment 8 JanKusanagi 2018-06-20 15:15:55 CEST 
2.9-2 in Cauldron works fine =)

Thanks!
JanKusanagi 2018-06-20 15:16:29 CEST

CC: (none) => jan-bugs

Comment 9 Jani Välimaa 2018-06-20 18:01:25 CEST 
Updated mga6 version to the latest version to also get latest upstream fixes.

Please test minitube-2.9-1.mga6 in core/updates_testing.

Assignee: jani.valimaa => qa-bugs

Comment 10 Johnny A. Solbu 2018-06-20 18:24:53 CEST 
It works on my mga6 x86_64 system. :-)

Whiteboard: MGA6TOO => MGA6TOO MGA6-64-OK

Comment 11 JanKusanagi 2018-06-20 19:50:03 CEST 
minitube-2.9-1.mga6 from core/updates_testing seems to work fine on a Mageia 6 machine I admin, too =)
Thomas Backlund 2018-06-20 20:28:08 CEST

Version: Cauldron => 6
CC: (none) => tmb
Whiteboard: MGA6TOO MGA6-64-OK => MGA6-64-OK

Comment 12 claire robinson 2018-06-24 22:12:44 CEST 
Validating. Advisoried (from comments).

Keywords: (none) => advisory, validated_update
CC: (none) => sysadmin-bugs

Comment 13 Mageia Robot 2018-06-25 00:03:30 CEST 
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2018-0123.html

Status: NEW => RESOLVED
Resolution: (none) => FIXED