Amanda Tarafa Mas comments

Results 132 comments of


                                            Amanda Tarafa Mas

Asp .net core does not prompt for access when user has removed access.

I'll reproduce later this afternoon and see what options are there to avoid/mitigate this. I'll update here when I know more.

Asp .net core does not prompt for access when user has removed access.

Thanks, I'm looking at a couple other things on my plate first. I'll still try to get to this later today.

Asp .net core does not prompt for access when user has removed access.

Just as a note, the linked you shared earlier, I think that by mistake you just copied the standard VS template for a ASP.NET Core 3 App, no code configuring...

Asp .net core does not prompt for access when user has removed access.

Yep, I downloaded it twice in the morning and just now before replying, I just see the standard template, standard Startup etc. But no worries, I've got working code, was...

Asp .net core does not prompt for access when user has removed access.

When a user revokes their permission for an app, code using `Google.Apis.Auth.AspNetCore*` may see exceptions in any of three different places, and unfortunately the exceptions are different each time. The...

Asp .net core does not prompt for access when user has removed access.

No I don't think it would be a rewrite, just to provide helper methods and similar to make it easier to handle this case. I'll know more when I have...

Asp .net core does not prompt for access when user has removed access.

(As a side note, if you have questions or run into issues with storing tokens or using in conjunction with Identity, please do create new issues for that to keep...

Asp .net core does not prompt for access when user has removed access.

Sounds good, I'll let you know when I start looking into it. It'll be a few weeks though.

Asp .net core does not prompt for access when user has removed access.

@meof-coding You need to follow three different approaches as described in my https://github.com/googleapis/google-api-dotnet-client/issues/1816#issuecomment-811769827. I understand this is far from ideal, but we haven't had the time to improve the error...

Support workload identity and default app credentials for GCS signed URLs and or provide example of how to sign the blob yourself

We might be able to offer some out of the box sopport for URL signing with external account credentials, but we need to confirm a few things first, so please...