I'm closing this for now, as the workaround in IGBF-1647 effectively makes this obsolete. File permissions will now be handled through dev-anon, which is unified between Agave and DE.

Good morning Nowlan! Thanks for the ticket regarding the discrepancy between the DE and Agave API download URLs. I was looking into it, and wanted to see what exact behavior you’ve seen when clicking on the Agave URL (https://agave.iplantc.org/files/v2/download/nowlanf/system/data.iplantcollaborative.org/nowlanf/test/igb-bam-seq.png
https://agave.iplantc.org/files/v2/download/nowlanf/system/data.iplantcollaborative.org/nowlanf/test/igb-bam-seq.png
)
When I click it, I get this in my browser
Pasted image at 2019-03-07, 8:55 AM

What’s strange is I was touching base with John Fonner about this, and the first time he clicked it he received a pems error in the browser. The second time, he saw what I see (it downloaded). So I’m curious if you see these pem errors intermittently or consistently.

Nowlan Freese [9:58 AM]
Hmm, that is interesting. Here's what I see from Agave when I check to see if that file is public:

{
"status": "success",
"message": null,
"version": "2.2.23-r7987f7e",
"result": [
{
"permission":

}
]
}
So it shouldn't be viewable, at least according to Agave.
Yesterday when I was talking with John Fonner, I also received a pems error when I tried the file. This morning I can view it as well.
From: https://agave.iplantc.org/files/v2/download/nowlanf/system/data.iplantcollaborative.org/nowlanf/test/igb-bam-seq.png

CIC Support [10:01 AM]
hmm, that is strange. Did you hit `https://agave.iplantc.org/files/v2/pems/system/data.iplantcollaborative.org/nowlanf/test/igb-bam-seq.png?pretty=true` to see those pems above?

Nowlan Freese [10:01 AM]
https://agave.iplantc.org/files/v2/pems/system/data.iplantcollaborative.org/nowlanf/test/igb-bam-seq.png?username=public&filter=permission

CIC Support [10:26 AM]
Thanks for the additional information, I’ll continue to look at this and reach back out with any additional questions and/or updates.

Nowlan Freese [10:34 AM]
No problem, thank you for looking into this.

CIC Support [12:15 PM]
Hi Nowlan, testing some stuff out and I wanted to see if it would be okay for me to grant public READ rights for a minute on this file? If you prefer to do it yourself, that works too

Nowlan Freese [12:15 PM]
Go for it, it's just an image we use for testing.

CIC Support [12:17 PM]
awesome, thanks!

Nowlan Freese [4:16 PM]
Hi Dr. Fonner. Quick question regarding public URL discrepancy between the Agave API and the Discovery Environment. For example, if a user within the DE clicks on Share > Create a Public Link..., then checks to see if that link is public through the Agave API, the DE link will be public, but the Agave API will say it is not public.
*Assuming the same file.

John Fonner [4:19 PM]
iRODS has some strange permissions behavior. I suspect that the DE is changing the underlying iRODS permissions, and Agave isn't picking up the change.
when you are checking through Agave, are you doing a permissions call (i.e. files-pems-list)?

Nowlan Freese [4:20 PM]
My GET looks like: https://agave.iplantc.org/files/v2/pems/system/data.iplantcollaborative.org/nowlanf/test/igb-bam-seq.png?username=public&filter=permission

John Fonner [4:21 PM]
does Agave also fail to download the file? Or it just fails to list "public" as having permissions?

Nowlan Freese [4:21 PM]
Agave fails to download as well.
We were doing testing, and initially assumed that DE/iRODS and Agave would be completely in sync, which led to some odd results.

John Fonner [4:23 PM]
A reasonable assumption, but unfortunately some of these capabilities sprang up in parallel. The DE doesn't share using Agave. It is using this: https://cyverse-de.github.io/api/endpoints/sharing.html
Still, I think this is updating permissions within iRODS. If that is the case, Agave should be able to pick up what happened.
I am about to have to step away from my desk, but we should document this as a bug report so that the core Agave devs can take a look.

Nowlan Freese [4:29 PM]
Sounds good, in the long run I don't think it affects us too much, but I could see it causing some user confusion if the file is public in one place and not another. Let me know if you would like me to write anything up.

John Fonner [4:30 PM]
It would be great if you could write up an example that they can reproduce. If you have a TACC account, you can submit that as a consulting ticket in portal.tacc.utexas.edu. If not, just paste it in here, and I'll submit the ticket on your behalf.
Thanks for catching this, Nowlan. Glad it isn't a show stopper for you.

Nowlan Freese [4:34 PM]
No problem, I do have a TACC account, so I will write it up as best I can. Thank you for all of your help, it's made a big difference for our project.

John Fonner [5:24 PM]
Glad to hear it. Well, it's a cool project. I hope you get the conference/paper recognition that you and your team deserve.