Question re. Globus Connect Personal endpoint

[Steven Timm]

I am trying to do a one-off upload of personal files from a local linux machine to our site globus server for purposes of a demo.  I have been asked to use the globus CLI to do so.

It is my understanding that I must install globus connect personal on the local linux box and I have done so.  Running as my unprivileged local user.  Through the Globus Web UI

I can see the directory and do the transfers to the main globus server successfully.

Through the globus CLI I can see the endpoint, list the endpoint, but when I try to transfer anything I get "permission denied". (i.e. globus lets me submit the transfer but the transfer then fails with "permission denied"

What would be the difference?  Is there a setting I can do with the CLI to make it work with the CLI?

[Gigi Kennedy]

Hi Steven,

For Transfers, not Uploads, if your transfer is encountering the error Permission Denied - “Path Not Allowed”, I would normally respond with the following.

 

This category of error that you’re encountering indicates that your identity may not have the appropriate permissions or there's a blocking policy in place (on the Endpoint hosting the Mapped Collection) preventing you from accessing the directory that the Mapped Collection is based on.

 

If you are logged in with the appropriate identity, we recommend directly contacting (via email) the Endpoint Admin(s) for further assistance as the Sharing Restrict Paths and/or Restrict Paths policies (enforced at the Mapped Collection and Storage-Gateway layers respectively) may need to be adjusted.

 

Please feel free to share the contents of this email with them, especially the error message you're encountering. If the Endpoint Admin(s) encounter any questions or concerns, please feel free to refer them to us and we'll be happy to help.

This is all assuming that you’re writing to a different path than the one you previously used while submitting the transfer via the webapp. Otherwise, I'd recommend opening a support ticket with us so that we could investigate further (sup...@globus.org). 

Hope this helps.

Best regards,

Gigi

Globus Help Desk

[Steven Timm]

Well, it's pretty clear that the permission problem was on the globus personal end because I had previously been able to make transfers from the other main endpoint to other endpoints (NERSC) and back, and I still can do that.

So the "Endpoints admin" of this globus personal installation is me.

But you mention above Uploads, where are they documented? 

I submitted the transfer via the web app, which worked, I cleaned those files out, and then attempted to submit the transfer again with the CLI and it didn't work.

[Gigi Kennedy]

Hi Steven,

> Well, it's pretty clear that the permission problem was on the globus personal end because I had previously been able to make transfers from the other main endpoint to other endpoints (NERSC) and back, and I still can do that.

So the "Endpoints admin" of this globus personal installation is me.

I apologize. Without having the Task ID# where this is occurring, I thought it was a different issue.

Please do open a ticket with support and we'll investigate further.

Please also send us the Task ID# of the transfer that is encountering the Permission Denied.

Thank you,

  Gigi

[Steven Timm]

It turns out that the problem was that my globus personal was configured to serve ~/ directory and I was trying to do / directory, that's why it was failing.

I can now transfer files and it works ok.