[Iplant-api-dev] Testing API Keys and Secrets

[Rion Dooley]

Confirmed. Agave and Foundation are both responsive and operational again.

--
Rion




On Sep 22, 2014, at 4:32 PM, Andy Edmonds <aedmonds at iplantcollaborative.org<mailto:aedmonds at iplantcollaborative.org>> wrote:

DNS issues are now resolved.

Thanks...
-Andy-

--
Andy Edmonds
University of Arizona
iPlant Collaborative
Core Services - Sr. Systems Administrator
Email: aedmonds at iplantcollaborative.org<mailto:aedmonds at iplantcollaborative.org>
Phone: 520-626-4279

On 09/22/2014 02:04 PM, Ramona Walls wrote:
Hey Dennis,

My api key is not working today either. James Carson said he is having the same problem and that there are DNS issues today which should be resolved by tomorrow.

Ramona

------------------------------------------------------
Ramona L. Walls, Ph.D.
Scientific Analyst
The iPlant Collaborative
Thomas J. Keating Bioresearch Building
1657 East Helen St
Tucson, AZ  85721
tel: 520.626.1489
fax: 520.626.4824
rwalls at iplantcollaborative.org<mailto:rwalls at iplantcollaborative.org>

On Mon, Sep 22, 2014 at 1:43 PM, Dennis Roberts <dennis at iplantcollaborative.org<mailto:dennis at iplantcollaborative.org>> wrote:
That sounds good. Thanks.

Dennis

On Sep 22, 2014, at 1:36 PM, Rion Dooley <dooley at tacc.utexas.edu<mailto:dooley at tacc.utexas.edu>> wrote:

The username and password doesn’t have to be good, just present. You get a different error message for a bad password than a bad client.

$ curl -sku “abcd123:efgh456" -X POST -d "grant_type=password&username=dennis&password=blahblah&scope=PRODUCTION" -H "Content-Type:application/x-www-form-urlencoded" https://agave.iplantc.org/token
{
    "error": "invalid_client”,
    "error_description": "Client Authentication was failed.”
}
$ curl -sku “$API_KEY:$API_SECRET" -X POST -d "grant_type=password&username=dennis&password=blahblah&scope=PRODUCTION" -H "Content-Type:application/x-www-form-urlencoded" https://agave.iplantc.org/token
{
    "error": "invalid_grant",
    "error_description": "Provided Authorization Grant is invalid."
}

--
Rion




On Sep 22, 2014, at 3:25 PM, Dennis Roberts <dennis at iplantcollaborative.org<mailto:dennis at iplantcollaborative.org>> wrote:

I was hoping to avoid having to have a known username and password configured in the DE if possible. Are there any other options? If not, I’ll use that option.

Thanks,
Dennis

On Sep 22, 2014, at 1:24 PM, Rion Dooley <dooley at tacc.utexas.edu<mailto:dooley at tacc.utexas.edu>> wrote:

You could try to authenticate with a known username and password using the API keys. That will throw an error if the keys are bad.

--
Rion




On Sep 22, 2014, at 3:21 PM, Dennis Roberts <dennis at iplantcollaborative.org<mailto:dennis at iplantcollaborative.org>> wrote:

I apologize if this question has an obvious answer, but I couldn’t find one in the documentation. Is there an Agave endpoint that I can hit in order to test only my Agave API key and secret to make sure that they’re valid? What I want to do is have some assurance that the authorization can succeed before I redirect the user.

Thanks,
Dennis


_______________________________________________
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





_______________________________________________
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/rwalls%40iplantcollaborative.org?unsub=1&unsubconfirm=1





_______________________________________________
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/aedmonds%40iplantcollaborative.org?unsub=1&unsubconfirm=1


_______________________________________________
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/20140922/8170c5b6/attachment-0001.html