As the middleware platform, we need to create an interface (using Cloudstreams) that will allow us to easily upload files to Google for many different end users and use cases.  The end goal of this interface will be a combination of automated integrations to pull files from oodles of sources to upload to various 'different' Google Drive specified group folders. In our instance of Google, we use service accounts to allow our application to drop into a any given Google drive where this service account was given write access.  (Go to drive, membership, input service account, provide content manager.)

While we were successfully able to create a connector with a service account, we are unable to create refresh tokens with said service account. (Apparently limitation on this type of authentication?!?!).  

I started this thread in the community to see if there are others out there that have solved this for their corporate Google stack.  Basically if we are unable to get a refresh token, then this cannot be automated. I feel like we are missing a key component here.  Any one have any insight on this?  (Note: we started a support ticket in Empower, but ultimately was only provided the existing PDF, which did not go into detials on this type of use case.)

Thanks

Hi Michelle,

Can you please share some more details like where are you using it and which connector.

I have tried some other google connector on cloud  like google big query and it support the refresh token mechanism.

Regards

Vikash Sharma

As the middleware platform, we need to create an interface (using Cloudstreams) that will allow us to easily upload files to Google for many different end users and use cases.  The end goal of this interface will be a combination of automated integrations to pull files from oodles of sources to upload to various 'different' Google Drive specified group folders. In our instance of Google, we use service accounts to allow our application to drop into a any given Google drive where this service account was given write access.  (Go to drive, membership, input service account, provide content manager.)

While we were successfully able to create a connector with a service account, we are unable to create refresh tokens with said service account. (Apparently limitation on this type of authentication?!?!).  

I started this thread in the community to see if there are others out there that have solved this for their corporate Google stack.  Basically if we are unable to get a refresh token, then this cannot be automated. I feel like we are missing a key component here.  Any one have any insight on this?  (Note: we started a support ticket in Empower, but ultimately was only provided the existing PDF, which did not go into detials on this type of use case.)

Thanks

Hi Vikash

We are using 10.11 Cloudstream on-prem (not webmethods.io) connector for Google drive in order to create interfaces to interact with our corporate files and folders in Google Workspace.

We are not familiar enough with Google to understand what exactly we need in order to establish the connection using the Google drive connection form.  

Any direction or insight on how to complete this form would be really helpful.  

Thank you so much.

Hi Michelle,

Can you please share some more details like where are you using it and which connector.

I have tried some other google connector on cloud  like google big query and it support the refresh token mechanism.

Regards

Vikash Sharma

As the middleware platform, we need to create an interface (using Cloudstreams) that will allow us to easily upload files to Google for many different end users and use cases.  The end goal of this interface will be a combination of automated integrations to pull files from oodles of sources to upload to various 'different' Google Drive specified group folders. In our instance of Google, we use service accounts to allow our application to drop into a any given Google drive where this service account was given write access.  (Go to drive, membership, input service account, provide content manager.)

While we were successfully able to create a connector with a service account, we are unable to create refresh tokens with said service account. (Apparently limitation on this type of authentication?!?!).  

I started this thread in the community to see if there are others out there that have solved this for their corporate Google stack.  Basically if we are unable to get a refresh token, then this cannot be automated. I feel like we are missing a key component here.  Any one have any insight on this?  (Note: we started a support ticket in Empower, but ultimately was only provided the existing PDF, which did not go into detials on this type of use case.)

Thanks