×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Except for maybe DMPOBJ.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Wednesday, December 14, 2011 10:37 AM
To: Midrange Systems Technical Discussion
Subject: Re: Storing an "OAuth consumer secret"
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/
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
