[
https://issues.apache.org/jira/browse/NIFI-13583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17872322#comment-17872322
]
Peter Turcsanyi commented on NIFI-13583:
----------------------------------------
[~juldrixx] I managed to replicate the issue on my NiFi-on-GKE environment. I
can confirm the behaviour on M4 vs M2.
Now I'm trying to identify which library upgrade caused the issue on M4.
NIFI-13268 affected only GRPC protocol level libraries, so I don't think this
is the culprit but I will check that too.
> Drive processor Credentials issue
> ---------------------------------
>
> Key: NIFI-13583
> URL: https://issues.apache.org/jira/browse/NIFI-13583
> Project: Apache NiFi
> Issue Type: Bug
> Affects Versions: 2.0.0-M4
> Reporter: Julien G.
> Priority: Major
> Attachments: EXAMPLE.json, example.webm
>
>
> When using a Drive processor with Default credentials, the processor fine at
> the beginning. But if we start a processor as ConsumePubSub, it won't work
> again with the following error. The only way to make it works again is by
> restarting NiFi. But if a GCP processor like ConsumePubSub is started it
> won't work again.
> {code:java}
> GET
> https://www.googleapis.com/drive/v3/files?includeItemsFromAllDrives=true&q='1yUM0-7Onq2U-3BcWsTAES-2WFzjehg3d'%20in%20parents%20and%20mimeType%20%3D%20'application/vnd.google-apps.folder'&supportsAllDrives=true
> {
> "code": 403,
> "details": [
> {
> "@type": "type.googleapis.com/google.rpc.ErrorInfo",
> "reason": "ACCESS_TOKEN_SCOPE_INSUFFICIENT",
> "domain": "googleapis.com",
> "metadata": {
> "method": "google.apps.drive.v3.DriveFiles.List",
> "service": "drive.googleapis.com"
> }
> }
> ],
> "errors": [
> {
> "domain": "global",
> "message": "Insufficient Permission",
> "reason": "insufficientPermissions"
> }
> ],
> "message": "Request had insufficient authentication scopes.",
> "status": "PERMISSION_DENIED"
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
