Re: Storing an "OAuth consumer secret"

["Raul A. Jager W." <raul@xxxxxxxxxx>]

edtf /qsys.lib/mylib.lib/myspace.usrspc'

You better encript it, a simple obfuscation may do, unless the source is 
easily accesible.


Rich Loeber wrote:

>   James,
>
>   If you want to protect them from "casual" inspection, then try using a
>   user space.  There is no command do easily display the contents the way
>   there is for a data area.  The APIs to store and retrieve information are
>   pretty simple to use.
>
>   Rich Loeber - @richloeber
>   Kisco Information Systems
>   [1]http://www.kisco.com
>   SDG
>
>   --------------------------------------------------------------------------
>
>   On 12/14/2011 1:05 PM, James Lampert wrote:
>
> On our current Google Calendar Integration project, I've managed to
> reach a point where I'm looking for a place to safely store the
> customer's "OAuth consumer secret" used to sign requests to the Google
> Apps web services, where it's at least safe from casual inspection.
>
> Any suggestions?
>
> --
> JHHL
>
> References
>
>   Visible links
>   1. http://www.kisco.com/
>