[Iplant-api-dev] Perl client for Agave API

[Matthew Vaughn]

I am in favor of exactly the behavior you're describing. A common set of client side behaviors would make everyone's life easier.


--

Matthew W. Vaughn, Ph.D.
Director, Life Sciences Computing
Texas Advanced Computing Center
The University of Texas at Austin
(949) 436-6642


________________________________
From: iplant-api-dev-bounces at iplantcollaborative.org [iplant-api-dev-bounces at iplantcollaborative.org] on behalf of Rion Dooley [dooley at tacc.utexas.edu]
Sent: Sunday, February 02, 2014 10:09 AM
To: Matthew Vaughn
Cc: iPlant API Developers Mailing List
Subject: Re: [Iplant-api-dev] Perl client for Agave API

Thanks for the great work, Cornel! I’m looking at the oauth2 branch and it looks like you’re expecting a token and/or client credentials to already be cached in a ~/.iplant.foundationalapi.json file on disk. The Agave CLI does the same thing (save storing the user’s password). It caches the following information:

{
    "access_token": "",
    "apikey": "",
    "apisecret": "",
    "created_at": "",
    "expires_in": "",
    "refresh_token": "",
    "username": ""
}

Would it make sense to standardize all the clients and have them consistently search for auth tokens in the following order?

1. Check for values explicitly passed in
2. Check the environment
3. Check the ~/.agave file on disk

 This might make development easier on some folks who might use one library or script to validate the behavior of another, or who are patching together multiple technologies. I think the Kurt has been taking a similar approach with rPlant. Perhaps he has some input.

--
Rion




On Feb 2, 2014, at 8:34 AM, Cornel Ghiban <ungreen at gmail.com<mailto:ungreen at gmail.com>> wrote:

Hi,

I've been working on this for a while and I'd like to get some feedback.
It needs polishing and documentation, but it's usable.

It started as a wrapper for v1 (see the code in v1 branch though) and I've updated it for v2.

https://github.com/cghiban/iPlant-FoundationalAPI

(yes, it needs to be renamed too).

For a quick start, look at the examples.

Thanks,
Cornel
_______________________________________________
Iplant-api-dev Mailing List: Iplant-api-dev at iplantcollaborative.org<mailto:Iplant-api-dev at iplantcollaborative.org>
List Info and Archives: http://mail.iplantcollaborative.org/mailman/listinfo/iplant-api-dev
One-click Unsubscribe: http://mail.iplantcollaborative.org/mailman/options/iplant-api-dev/dooley%40tacc.utexas.edu?unsub=1&unsubconfirm=1

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iplantcollaborative.org/pipermail/iplant-api-dev/attachments/20140202/926e0e39/attachment.html