AnsweredAssumed Answered

How can we use a "secure" or sensitive string as part of a web request action?

Question asked by syates21 on Sep 16, 2014
Latest reply on Jan 18, 2018 by paulwillen

It seems like sensitive workflow constants in NW2010 are *extremely* restricted in where they can be referenced.  I understand the sensitivity, but it also can make them not particularly useful.  For instance, if you want to make an OAuth call with Call Web Request, you'll need to pass the bearer token as an HTTP header.  This is typically a value that's pretty sensitive, but I can't find a way to actually plug in a value that wouldn't be trivially easy for a site owner/workflow designer to obtain.


Any ideas?