[Iplant-api-dev] Logging into AGAVE API with iPlant credentials

Fri Nov 15 13:23:11 MST 2013

The single quotes work. Thanks!

When I tried to create a key using
https://iplant-dev.tacc.utexas.edu/v2/auth, I get the following message:

<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a href="
https://iplant-dev.tacc.utexas.edu/v2/auth/">here</a>.</p>
<hr>
<address>Apache/2.2.25 (CentOS) Server at iplant-dev.tacc.utexas.edu Port
443</address>
</body></html>

I think I will just wait until Monday until the production version is up
and try it again. I don't really need to use it today. I'm also psyched to
try out Agave CLI.

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

On Fri, Nov 15, 2013 at 1:03 PM, Rion Dooley <dooley at tacc.utexas.edu> wrote:

>  The Agave beta api is hosted at https://iplant-dev.tacc.utexas.edu/v2
>
>  You MUST pull a token from the auth service and use that to interact
> with any of the other services. Your u/p will not work when calling any of
> the Agave services directly
>
>  The error you see is from Bash itself. Try single quoting your u/p (ex.
> curl -sku 'username:pA$$worD!' -XPOST -d "lifetime=3600"
> https://iplant-dev.tacc.utexas.edu/v2/auth/). Life will get a LOT easier
> for you if you use the Agave CLI. There's nothing to "install." Just
> download it and add the bin directory to your path. When you use the CLI,
> you can see the generated curl commands by adding the -V flag to any
> command. The -h option gives you the usage.
>
>  I would like to reiterate that this is the beta instance of Agave. The
> production version is up now and we're just waiting on DNS (and me to land
> in Denver) to announce it. You can expect to see an update in the
> documentation and tutorials on Monday to reflect the production version.
>
> --
> Rion
>
>
>
>
>
>  On Nov 15, 2013, at 12:36 PM, Ramona Walls <
> rwalls at iplantcollaborative.org>
>  wrote:
>
>  According to the tutorials (
> http://agaveapi.co/getting-started-with-the-agave-api/) I should be able
> to access the AGAVE API with my iPlant login. It is not working for me. I
> just use the Foundation API to create a token, so I know I am typing the
> curl command correctly. Do I need special permission to use AGAVE?
>
> On a side note, if I try to use curl (with either AGAVE or Foundation)
> with "my_user_name:my_password", I get an error (-bash: !": event not
> found) because my password ends in an exclamation point. It doesn't work if
> I double quote it either, but it works if I just leave it out and enter the
> password separately. I can change my password, but it would be nice if
> users' passwords could end in special characters.
>
> 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
>   _______________________________________________
> Iplant-api-dev Mailing List: 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/20131115/a321f587/attachment-0001.html 