Closed (won't fix)
Project:
Webform to Google Docs
Version:
7.x-4.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
12 Nov 2012 at 11:14 UTC
Updated:
20 Oct 2015 at 21:47 UTC
Jump to comment: Most recent
Comments
Comment #1
bjlewis2 commentedupdated title...
Comment #2
charlie-s commentedMy vote is to just hide the password when the settings page is pulled back up. Encrypting / decrypting is easy enough, but I would either have to build in the private key storage or depend on a Drupal 2-way encryption module, which just seems like too much work for not enough reward. Likewise, we ought to have a permission to use the Google Docs part of a Webform and a separate permission to allow the configuration of webform_to_gdocs.
Let me add a warning to this – anyone with PHP access (PHP input filter, Devel PHP snippet, etc) on your site can grab the password, even if it was decrypted. For this reason, when I use this module on sites I create a new Google account specifically for this and assume that any admins on the site should be trusted with access to this account.
Comment #3
bjlewis2 commentedI agree with everything above.
It would be good to have "configure webform to google docs login info" and "configure google docs on own/any webforms" permissions.
It would also be handy if you could set a different google account per user (that applies to all of their webforms), or per form.
Maybe these should be in the features request queue, but since it was mentioned here already...
Back to the original point, hiding the password after save would be sufficient for me for now.
Thanks!
Comment #4
charlie-s commentedNo longer relevant since we use Oauth + Google Drive API.