You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even if you remove the permissions of the shares from Aspera Shares, reauthorize the "mkdir" again, and start all the Background Jobs.
It looks like ascli doesn't have the right permissions.
ascli only uses the APIs, and the API call is correct here.
It seems to be rather an inconsistency in Shares side:
Shares web UI requires both "mkdir" and "browse" permissions to create a folder.
Shares API requires both "mkdir" and "rename" permissions for the same
Enter a ticket to IBM Aspera Support.
Note: It takes by default 10 minutes for changes in rights take 10 minutes to be active after change. This can be changed in the admin page, at least for testing.... (I changed to 1 min for the tests)
Hello.
Even if you remove the permissions of the shares from Aspera Shares, reauthorize the "mkdir" again, and start all the Background Jobs.
It looks like ascli doesn't have the right permissions.
The text was updated successfully, but these errors were encountered: