Thanks. "Tricky" I might be able to deal with. "Where to store" sounds
like this isn't a completed feature yet.
True? Does this feature work yet?
Rob
On 4/5/24 12:31 AM, [email protected] wrote:
Hi Rob,
When using XOAUTH2 the transform does not expect a password in the
password field but an OAuth 2 token [1]. Obtaining this token from
Google is a bit tricky. We could create GUI elements to fetch that token
and this might be a solution for the GUI, but it won't be a real
deployment solution. We would also have to think about where we store
these tokens in a safe way (they are linked to the user that has signed
in during the OAuth flow).
A more future proof solution would be to create Gmail transforms that
can use a service account or use the IAM role defined on the resource
they are currently using.
Kr,
Hans
[1]
https://developers.google.com/gmail/imap/xoauth2-protocol#the_sasl_xoauth2_mechanism
On 5 Apr 2024 at 00:38 +0200, Rob Brandt <[email protected]>, wrote:
Hi. I am new to hop although I have done extensive transformations in
Pentaho kettle from time to time. I found my way to hop because I am
looking for a way to retrieve emails and with their attachments from
gmail.
Starting a year or three ago, Gmail stopped supporting what they call
"less secure" 3rd party applications. What they DO support is Oauth. I
have this particular account I want to access configured for that, for
example in Mozilla Thunderbird.
So I have gotten hop and installed it, and created a workflow to access
this account. I have configured it with the information I have,
specified Oauth authentication, input the username and password, and
tested it. It fails.
Does anyone have experience with this? A step by step? Any clues?
Thanks
Rob
