[Iplant-api-dev] Problems creating an API Client SOLVED

[Damian Gessler]

Follow up:

SSL errors on curl 7.19.7 on an iMac OS-X 10.6.8:
curl: (35) error:14077458:SSL routines:SSL23_GET_SERVER_HELLO:reason(1112)

But got it working by adding the -3 option to the Basic Auth header, e.g.:

curl -3 -H 'Authorization : Basic <base64(username:password)>' -X POST 
-d 'clientName=myClientName&tier=UNLIMITED&description=My 
description&callbackUrl=null' 
https://agave.iplantc.org/clients/v2/?pretty=true


On 5/7/14 2:55 PM, Joe Stubbs wrote:
> Hi Damian,
>
> It looks like there is an issue on the developer site. We'll get that
> sorted out asap and let you know. In the meantime, you should be able to
> use another http client such as curl or Chome's Postman, as those have
> been working fine.  For example,
>
> curl -H "Authorization: Basic <base64(u:p)>"
> "https://agave.iplantc.org/clients/v2"
>
> Joe
>
>
> On 05/07/2014 03:34 PM, Damian Gessler wrote:
>> Hi Joe,
>>
>> Still getting the same errors, except now on the live-docs page
>> (http://agaveapi.co/live-docs/#!/clients/create_post_1) it responds:
>>
>> {
>>      "status": "error",
>>      "message": "Invalid Authorization header format.",
>>      "version": "2.0.0-SNAPSHOT-rc3fad",
>>      "result": {}
>> }
>>
>> This is after a fresh login.
>>
>> The HTTP response status code is 401 (Unauthorized), which is not one
>> codes documented on the page as possible expected response.
>>
>> Damian.
>>
>> On 5/7/14 1:16 PM, Joe Stubbs wrote:
>>> All,
>>>
>>> We are very sorry for the inconvenience. The services should be back up
>>> and running now. We had a resource issue on our mysql server which
>>> caused the outage.
>>>
>>> Please let us know if you continue to experience any issues.
>>>
>>> Best,
>>> Joe
>>>
>>>
>>> On 05/07/2014 01:03 PM, Damian Gessler wrote:
>>>> I am using my iPlant credentials, re the instructions at
>>>> https://github.com/iPlantCollaborativeOpenSource/iplant-agave-sdk/blob/master/docs/client-create.md.
>>>>
>>>> D.
>>>>
>>>> On 5/7/14 12:01 PM, Rion Dooley wrote:
>>>>> Are you using http basic auth in your curl command with your iplant
>>>>> credentials?
>>>>>
>>>>> -
>>>>> Rion
>>>>>
>>>>> ----- Reply message -----
>>>>> From: "Damian Gessler" <dgessler at iplantcollaborative.org>
>>>>> To: "Rion Dooley" <dooley at tacc.utexas.edu>
>>>>> Cc: "Discussion of iPlant API development"
>>>>> <iplant-api-dev at iplantcollaborative.org>
>>>>> Subject: [Iplant-api-dev] Problems creating an API Client
>>>>> Date: Wed, May 7, 2014 12:48 PM
>>>>>
>>>>> Is OAuth client-create up today (SSL errors?)? I am trying to create an
>>>>> OAuth2 Client and get the following errors:
>>>>>
>>>>> 1. Following
>>>>> https://github.com/iPlantCollaborativeOpenSource/iplant-agave-sdk/blob/master/docs/client-create.md
>>>>>
>>>>> (i.e., using bin/clients-create), the response is:
>>>>>
>>>>> EXPECTED value GOT EOF
>>>>> EXPECTED value GOT EOF
>>>>>
>>>>>
>>>>> 2. Logging in and trying
>>>>> http://agaveapi.co/live-docs/#!/clients/create_post_1, the response is:
>>>>>
>>>>> Response Body
>>>>> no content
>>>>> Response Code
>>>>> 0
>>>>> Response Headers
>>>>> {}
>>>>>
>>>>>
>>>>> 3. Writing and executing my own curl command line, there is no textual
>>>>> response and curl's return code is 35, which means:
>>>>>
>>>>> 35     SSL connect error. The SSL handshaking failed.
>>>>>
>>>>> This occurs for both hosturl=https://agave.iplantc.org and
>>>>> https://agave.iplantc.org:443
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>> _______________________________________________
>>>> 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/jstubbs%40tacc.utexas.edu?unsub=1&unsubconfirm=1
>>> _______________________________________________
>>> 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/dgessler%40iplantcollaborative.org?unsub=1&unsubconfirm=1
>>>
>> _______________________________________________
>> 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/jstubbs%40tacc.utexas.edu?unsub=1&unsubconfirm=1
>
> _______________________________________________
> 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/dgessler%40iplantcollaborative.org?unsub=1&unsubconfirm=1
>