[Iplant-api-dev] erratic behavior

[Rion Dooley]

We identified a bug in the auth filter running across many of the Agave APIs that was dropping usernames under certain concurrency conditions. This resulted in an very small, isolated tenancy leak which, from what we have identified, was isolated to system listings. A patch was just pushed into production which should both restore the proper system listings and fix the issue several of you saw where you received intermittent empty responses when querying for system listings. If you continue to notice any issues, please let us know asap. No additional action should be needed on your part.

--
Rion




On Aug 5, 2014, at 7:20 PM, Dennis Roberts <dennis at iplantcollaborative.org<mailto:dennis at iplantcollaborative.org>> wrote:

I've seen similar behavior when trying to submit jobs from the DE and from the Agave live docs. I received the permission denied error that Roger is referring to for every job I’ve tried to submit today. The age of the token had no effect on whether or not I could submit the job. I was also able to continue listing apps with the same token after the job submission failure.

Thanks,
Dennis

On Aug 5, 2014, at 4:38 PM, Rion Dooley <dooley at tacc.utexas.edu<mailto:dooley at tacc.utexas.edu>> wrote:

To what system were you trying to register an app? The permission errors seem consistent. When you create and refresh your token,  add a -V flag and see what grant type it is using. Older versions of the cli did not use the password grant type, so they would sporradically fail to refresh when tokens were pulled in different contexts .

Rion
________________________________________
From: iplant-api-dev-bounces at iplantcollaborative.org<mailto:iplant-api-dev-bounces at iplantcollaborative.org> [iplant-api-dev-bounces at iplantcollaborative.org<mailto:iplant-api-dev-bounces at iplantcollaborative.org>] on behalf of Barthelson, Roger A - (rogerab) [rogerab at email.arizona.edu<mailto:rogerab at email.arizona.edu>]
Sent: Tuesday, August 05, 2014 6:23 PM
To: Rion Dooley
Cc: Discussion of iPlant API development
Subject: [Iplant-api-dev] erratic behavior

I have been trying to work with Agave this afternoon, but it seems rather inconsistent and very odd in its behavior. For example I tried to register an app, but I got this message:
Permission denied. You must authenticate to register an application.
I had a fairly fresh token, but tried creating a new token.
But I still got the same message. I tried running auth-check and it said
Current token is expired.
I ran auth-tokens-refresh and got this:
{"error":"invalid_grant","error_description":"Provided Authorization Grant is invalid.”}
I ran auth-tokens-create to get a new token and that ran okay.
I tried adding a new app and I got this again:
Permission denied. You must authenticate to register an application.

So I don’t understand what is going on.

Roger



--
Roger Barthelson Ph.D.
Scientific Analyst
iPlant Collaborative
BIO5 Institute, University of Arizona
Phone: 520-977-5249
Email: rogerab at email.arizona.edu<mailto:rogerab at email.arizona.edu><mailto:rogerab at email.arizona.edu>
Web: www.iplantcollaborative.org/<http://www.iplantcollaborative.org/><http://www.iplantcollaborative.org/>

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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iplantcollaborative.org/pipermail/iplant-api-dev/attachments/20140806/ec3b4d8a/attachment-0001.html