Google API Authentication & REST Nodes

I use a lot of APIs from Google, all which require access tokens. I have a lot of daily data ingestion jobs I would like to move to KNIME Hub for automation. Today, the Palladian OAuth nodes + REST execution work perfectly for what I need when I run locally, but the Palladian nodes aren’t available on Hub. I tried using the Google Authenticator with a JSON API Key, but I can’t get that to work with REST. I need the flexibility of REST over built in nodes like Drive or Analytics because those don’t allow for the customization I need for the requests.

I see someone else had a similar request here: Can't connect to Google Cloud API (others than those with specific nodes)

Any solutions? Or can I enter a huge plea to have a way to license Palladian Nodes for Hub?

Hey @digDataAnalytics,

Thanks for your post; I think it could be helpful for other KNIMErs out there.

I guess the answer to how to interact with Google APIs within KNIME Business Hub is the Secret Store.:key:

You can create your secrets on a personal level with interactive or service authentication mode or team level using only a service account to authenticate.

Then to use your secret in a workflow, it will look like this :point_down:t2:

Let me know if this could solve your use case with KNIME Hub Google and Rest nodes.

2 Likes

Hi digDataAnalytics,

Great to hear that the OAuth nodes are helpful!

  1. If you’re using a local “Server” or “Hub”, you can easily obtain a yearly license for the Palladian Nodes yourself.

  2. If the KNIME company wants to license these nodes for running them on their hosted / SAAS offerings to offer it to their end users, we’re open to that.

  3. I’d be very curious to hear about your use case of these nodes and if there’s anything we can improve in general - if you’d like to have a chat, feel free to get in touch with me directly at mail@palladian.ws

Best regards,
Philipp

1 Like

I am on a paid Team plan, not Business Hub. Looks like stored secrets is only an option on the business hub?

Hey @digDataAnalytics, thanks for providing more information.

I think I have overlooked one thing: :see_no_evil:

You don’t necessarily need to use the Secret Store if you authenticate with a service account by providing the JSON file containing your API keys. The challenge here, which can be a bit tricky, is ensuring that the JSON file is placed in a location where the Google Authenticator node can access it. You can store it in the workflow itself, in the workflow data folder, or in a designated space within your Community Hub Team.

It is explained better in this guide :link:

You can use the credentials output port from the Google Authenticator node to connect directly to the REST client nodes. In the authentication tab, the “Credentials (input port)” option will be automatically selected. See the image below for reference. :point_down:t2:

You’re correct; the secret store is currently only available for Business Hub, but there are plans to expand its availability soon, including it in the Community Hub Team plan offer.

A preview version is ready, and we were wondering if you might be interested in testing it out and exploring its features. :computer_mouse: :hammer_and_wrench:

Thank you again, and I hope some of the resources prove helpful to you.

1 Like