Google Apps脚本附加组件源代码/安全性 [英] Google Apps Script Add-On Source Code/Security

查看:77
本文介绍了Google Apps脚本附加组件源代码/安全性的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在构建Google Apps脚本附加组件,并想知道任何人在将其发布到Marketplace时是否可以访问基础源代码?我想在代码中存储密码/私钥,并且要确保没有人安装应用程序可以访问它。

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.

使用Google Apps脚本库允许用户可以使用他们自己的脚本进入源代码,这是一个公共库的例子,其源代码对最终用户是可见的。

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?

谢谢。

推荐答案

评论 < a href =https://stackoverflow.com/users/3556215/st3ph> St3ph


你可以检查这个页面 https://developers.google.com/apps-script/guides/properties第一个选项卡说明可以存储在道具中的数据类型ERTIES。对于你的情况,scriptproperties是最好的。表中提到的所有用户都是可以访问代码的用户,访问插件的用户无法访问代码。

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.

这篇关于Google Apps脚本附加组件源代码/安全性的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆