3
votes

I'm building a Google Apps Script Add-On and wanted to know whether anyone can access the underlying source code when I publish it to the Marketplace? I want to store a password/private key in the code and wanted to make sure no one who installs the app can access it.

Using a Google Apps Script Library allows a user to use their own script to step into the source code, so that's an example of a public library whose source code is visible to the end user.

Failing that, is there a better solution for storing a password/private key?

Thank you.

1
you cant see server side code which is where your passwords and such should live.Zig Mandel
You can check this page developers.google.com/apps-script/guides/properties first tab explain what kind of data you can store in properties. For your case scriptproperties is the best one. The all users mention in the table are users who can access the code, users who access addon don't have access to the code.St3ph
Hi St3ph, thanks for the answer, that seems like a perfect fit for what I need.Zahir Ally

1 Answers

1
votes

From the comment by St3ph

You can check this page https://developers.google.com/apps-script/guides/properties first tab explain what kind of data you can store in properties. For your case scriptproperties is the best one. The all users mention in the table are users who can access the code, users who access addon don't have access to the code.