Hi everyone,
I've been using the Google Authentication Core asset (https://www.outsystems.com/forge/component-overview/10251/google-authentication-core) to allow my logged-in users to interact with Google APIs, and everything was working smoothly.
Due to the architecture of my app, I recently needed to start allowing virtual users (which are users who log in to my application through OutSystems standard login rather than Google login) to access certain Google resources.
To achieve this, I created a google service account, followed the setup procedures and after some reaserch I was able to find the Service Account Google Token asset (https://www.outsystems.com/forge/component-overview/14027/service-account-google-token), which allows me to obtain the access token for interacting with Google APIs.
Since the only action I need from this asset was the one to generate the token, which is called GoogleToken, I tried to copy it to the GoogleAuthenticationCore module of the Google Authentication Core Asset (which I had successfully edited in the past). However, with only having added the dependency of the CreateToken action from the JTW_Core module of the JWT service, I encountered an error during the 1-Publish step, specifically "Incompatible Producers: There are producer modules that were compiled with an outdated OutSystems Server. Please republish your factory."
Note that this error did not occur when I published the ServiceAccountConector module from the Service Account Google Token asset.
In this thread https://www.outsystems.com/forums/discussion/72420/how-to-fix-this-error/, another developer stated to have had the same issue, but the proposed solutions did not work in my case.
Does anyone have any clue as to how to solve this issue?
Thank you!
Hi Bruno
First, when you want to make alterations to a forge component, copy the component for your application so that new versions can not destroy the changes that you have made.
Did you download the forge components for the correct versions? After you downloaded them, were you able to publish them to your currenct version? Then you have a good startpoint to create your own copy of a component, and alter it like you want it.
Best regards, Marlies