PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Password'ify the support key field

  1. I bought the developer key so that I can get automagic updates on multiple sites that I maintain. In a number of those sites, I am not the only admin who would have access to the settings area for Gravity Forms. While I'm not extremely worried that any of the other admin / developers would take my support key - if a site were to be compromised the key would be accessible to all.

    Storing it as a password (both field type on screen and secured in database) would allieviate these concerns, help you ensure that those who have paid for support are (only) the ones making use of it, and be a relatively easy thing to implement I would expect. Wordpress has great reference code I think :P

    Posted 9 years ago on Thursday September 10, 2009 | Permalink
  2. You are the second person in as many days to suggest this change. We will look into how to best handle it. It's a good idea and makes sense for developers with client sites. We will see what we can do.

    Posted 9 years ago on Thursday September 10, 2009 | Permalink
  3. This is a much needed feature, I bought the developer license for client sites but I sometimes hire extra developers who then have access to my key.. Although I trust them, I don't want them to be able to use my key..

    Posted 9 years ago on Monday September 14, 2009 | Permalink
  4. This feature will be in the 1.1 release that we are getting ready to send out. The license key acts as a password field on the Settings page and the value is hashed in the database.

    Posted 9 years ago on Monday September 14, 2009 | Permalink

This topic has been resolved and has been closed to new replies.