HISE Logo Forum
    • Categories
    • Register
    • Login

    Best Practices for Storing Consumer Key / Secret in Licensing Script

    Scheduled Pinned Locked Moved Scripting
    3 Posts 2 Posters 302 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Casey KolbC
      Casey Kolb
      last edited by Casey Kolb

      On the topic of licensing, I'm trying to cover all of my bases here so I don't get mega-hacked 😱 For those of you who are activating licenses via an online server, how do you approach including your consumer key and secret in your code? It feels too simple to just place them in variables in HISEScript, especially if your committing to a private GitHub repository.

      Casey Kolb
      Founder & CEO of Lunacy Audio
      Composer | Producer | Software Developer

      1 Reply Last reply Reply Quote 0
      • Christoph HartC
        Christoph Hart
        last edited by

        If your repository gets hacked your product is hacked so it‘s no problem storing the key in plain text there.

        1 Reply Last reply Reply Quote 0
        • Casey KolbC
          Casey Kolb
          last edited by

          Right, that makes sense. Just wondering if there's a more secretive way to securely include that info. I'm sure it's fine for now.

          Casey Kolb
          Founder & CEO of Lunacy Audio
          Composer | Producer | Software Developer

          1 Reply Last reply Reply Quote 0
          • First post
            Last post

          39

          Online

          1.7k

          Users

          11.7k

          Topics

          102.1k

          Posts