Leo

Unfortunately this is WAI. We don't allow developers to allow both email/password and email/link. If you allow email/link, email/password will not be a supported sign-in method, and previous users using...

Yep, this is one of the features we plan on implementing soon. Email link sign in may come first though.

I spoke to @bojeil-google about this and he brought up a good point - we should only require explicit consent when the user is signing up, which is an issue...

@iamyaoxi We're still discussing this internally, we'll get back to you once we decide on a solution. I'd suggest not doing too much work until then.

Quick update, our UX person is new and still ramping up so it may take a little longer than normal. I'll get back to you once we figure it out....

@pragatimodi mind taking a look?

Hi @laurensknoll, you can create your own [custom credential supplier](https://github.com/googleapis/google-auth-library-python/blob/main/docs/user-guide.rst#accessing-resources-using-a-custom-supplier-with-oidc-or-saml). This approach is much more flexible.

It's covered in the user guide [here](https://cloud.google.com/iam/docs/workload-identity-federation-with-other-clouds). Are you using EC2? What you've provided is not enough for us to help. If you provide more info (e.g. the config you're...

The library methods here return UserCredentials. Is this compatible with BYOID? We have ExternalAccountAuthorizedUserCredentials for BYOID.

> > The library methods here return UserCredentials. Is this compatible with BYOID? We have ExternalAccountAuthorizedUserCredentials for BYOID. > > `ExternalAccountAuthorizedUserCredentials` won't need any changes to have the capability of...