Closed jvendetti closed 1 year ago
Hello, feedback on this (6 months after), while merging this to our code base (Agroportal) I figured out that the Google Analytics ID is public, you can see it if you visit the sources of the pages (view-source:https://bioportal.bioontology.org/), not sure on how they verify the provenance as I can just take your analytic ID and put it in my website?
But anyway, as it is publicly available I don't think we should put it as a credential, it makes things just more complicated to update.
@alexskr - I'm having trouble remembering the conversation where this was discussed / decided upon:
@alexskr and I decided to store BioPortal's GA4 measurement ID in encrypted credentials as one way to safeguard against our ID getting inadvertently used by OntoPortal virtual appliance instances.
Do you remember the reasoning behind putting this in the credentials file? (See comment from Syphax directly above).
I don't recall exactly why we decided use encrypted credentials to store google analytics tag but somehow we thought it was reasonable. There is no technical requirement to store it in the encrypted credentials so moving it out should not be a problem.
Contains the necessary changes to migrate from Universal Analytics to Google Analytics 4. Resolves #270.
@alexskr and I decided to store BioPortal's GA4 measurement ID in encrypted credentials as one way to safeguard against our ID getting inadvertently used by OntoPortal virtual appliance instances.
If appliances want to use GA4, they'll need to add their measurement ID to the relevant credential file: