We recommend switching to the latest versions of Edge, Firefox, Chrome or Safari. Using Internet Explorer will result in a loss of website functionality.

Passing API Key (connect to govern) in http node as an encrypted variable

Comments

3 comments

  • Avatar
    Gerard Cafaro

    At the node or data flow level, you can define new properties that hold your API Key and Secret. These fields can be defined as the "Password" field type to encrypt them and hide them in the UI. It's recommended to define these as properties at the data flow level so that they can be reused throughout your flow:

    More information on this can be found in our Defining Properties doc.

     

    Then within your HTTP nodes, you can reference these fields with this syntax:

    Authorization: {{^key^}};{{^secret^}}

    The {{^key^}} syntax means to insert the value stored within the key property. You can either copy/paste that into your header field directly if you used the same property names as me, or you can insert your properties via the header field's menu:

     

    0
    Comment actions Permalink
  • Avatar
    Gary Allemann

    Thank you. I was passing the full string and it wasn't being recognised. 

     

    This is working for me :)

    0
    Comment actions Permalink
  • Avatar
    Patrick Magee

    another alternative is using Run Property Sets, define the run property set and pass this to any dataflow which may need the same key/secret or api credentials. 

    0
    Comment actions Permalink

Please sign in to leave a comment.