8.4.4 requires serviceusage.services.use permission on google cloud?

[Dylan Buth]

Hey everyone. Hope this is the right place. 

Two employees at my company use Cyberduck daily. One is on 7.7.2 and has no issues. The other is on 8.4.4 and started getting authentication errors when trying to connect to google cloud storage.

Listing directory / failed.
us...@domain.com(fake email obviously) does not have serviceusage.services.use access to the Google Cloud project.

His permissions haven't changed, and he has the same as the other employee using Cyberduck 7.7.2. I went to add the permission thinking maybe a new feature requires it or something, but when adding it, it shows the status of the permission is "Testing" with a warning, "Not recommended for production use". This is blocking the employee from doing his job so I added it and Cyberduck seems to be working fine for him. 

Is this a bug with the most recent version? What would Cyberduck be doing that would require this permission? Has anyone else run into this with 8.4.4? I suppose it could be any version between 7.7.2 and 8.4.4. Not sure when he upgraded or what he upgraded from. 

[David Kocher]

We are tracking this issue in https://github.com/iterate-ch/cyberduck/issues/13745

— David

> On 20 Sep 2022, at 17:43, Dylan Buth <db...@bluemill.us> wrote:
>
> Hey everyone. Hope this is the right place.
>
> Two employees at my company use Cyberduck daily. One is on 7.7.2 and has no issues. The other is on 8.4.4 and started getting authentication errors when trying to connect to google cloud storage.
>
> Listing directory / failed.
> us...@domain.com(fake email obviously) does not have serviceusage.services.use access to the Google Cloud project.
>
> His permissions haven't changed, and he has the same as the other employee using Cyberduck 7.7.2. I went to add the permission thinking maybe a new feature requires it or something, but when adding it, it shows the status of the permission is "Testing" with a warning, "Not recommended for production use". This is blocking the employee from doing his job so I added it and Cyberduck seems to be working fine for him.
>

> <image.png>
>
> Is this a bug with the most recent version? What would Cyberduck be doing that would require this permission? Has anyone else run into this with 8.4.4? I suppose it could be any version between 7.7.2 and 8.4.4. Not sure when he upgraded or what he upgraded from.
>

> --
> --
> You received this message because you are subscribed to the Google Groups "Cyberduck" group. To post to this group, send email to cybe...@googlegroups.com
> To unsubscribe from this group, send email to cyberduck+...@googlegroups.com
> For more options, visit this group at https://groups.google.com/group/cyberduck
> --
> Post bug reports and feature requests
> https://trac.cyberduck.io/newticket
> --
> Support development
> https://cyberduck.io/donate/
> ---
> You received this message because you are subscribed to the Google Groups "Cyberduck" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to cyberduck+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/cyberduck/630c752f-95fe-4e65-afe3-40417a5d9812n%40googlegroups.com.
> <image.png>