Authentication happens in the configuration window. By default, credentials are stored in memory. Custom credentials can be set in the configuration window. A custom credential location is useful for sharing the credentials via a KNIME Server or for exposing the user credentials.
After choosing the credential location, one must authenticate using the "Authenticate" button. A pop-up will appear that asks the user to grant access to the selected scopes. If you have already authenticated, the "Authenticate" will test the stored credentials in the selected location. Credentials can be manually deleted by clicking on the "Clear Selected Credentials" button.
Access can be revoked at any time by visiting myaccount.google.com/permissions
For details see: developers.google.com/analytics/resources/concepts/gaConceptsAccounts.
Describes the state of the authentication.
The authentication credentials will be kept in memory. They are discarded when exiting KNIME.
The authentication credentials will be saved in separate file in the given directory.
Select Directory
The directory to which the credentials should be saved.
The authentication credentials will be saved in the node settings.
Selects all scopes, so the credentials can be used with all available Google Connection nodes.
You want to see the source code for this node? Click the following button and we’ll use our super-powers to find it for you.
A zipped version of the software site can be downloaded here.
Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.
Try NodePit Runner!