We are trying to set up a share for people who will not be able to install the WD MyCloud desktop client on their machines. So it has to be browser-based access.
We can use http://wdmycloudex2.devicexxxxxxx.wd2go.com/ to login, and then the Web File Viewer to access the share and navigate round the folder structure. But when a normal user right-clicks on a file, all of the file-handling operations (download, copy, move, delete, etc) are greyed out. This is on up-to-date Windows 7, with IE or Firefox. As far as we can see, all permissions are set up correctly for the users, groups and shares.
The same user can access the share AND perform all permitted operations (e.g. read or read/write) when using the WD MyCloud desktop client.
If the admin user logs in via the browser interface, then they have full capability. And if the normal user then logs in immediately after admin , then they too have full access - the file-handling operations are all there. But this only lasts for a few minutes.
We can’t see any cookies stored by the browser. So we think that when admin logs in, a memory-resident ticket is created in the client machine, which persists after admin has logged out - and so is used when the normal user logs in - but which expires after a few minutes.
Can anyone explain what is going on? And especially how can we give read or read/write access to normal users who come through the browser interface? Are we missing something in setting up the permissions?