OSX Finder shows a bit unwanted behavior when it comes to handling permission issues. On Windows, everything works correctly, OSX 10.6.x has an issue with moving files, OSX 10.7.x. shows issues when moving, renaming and deleting files. Note that I'm not sure if this issue is related to Adobe Drive or to how OSX works internally.
Moving files - an issue with 10.6.x and 10.7.x
When a user moves files to a location where they don't not have permissions to create a file, OSX Finder shows a system login dialog where you can enter your OSX username and password. After entering the credentials (which aren't the credentials of the DAM server) nothing happens, the file stays in it's original location and no error is shown to the user.
In this case I would expect to get an error dialog which tells the user it doesn't have permissions to move the file. The OSX login dialog doesn't provide anything in this case as it doesn't allow you to login as a different Drive user.
Error in the AD log when moving files
2012/04/23 16:43:02,825 [ConnectionHandler-kernel] ERROR AbstractHandler - com.adobe.drive.data.model.DriveException: com.adobe.drive.data.manager.exception.PermissionDeniedException: Asset is unlocked (ID: 1050 | Field of Sunflowers.jpg | FILE | VISIBLE)
com.adobe.drive.biz.filesystem.FileSystemException: com.adobe.drive.data.model.DriveException: com.adobe.drive.data.manager.exception.PermissionDeniedException: Asset is unlocked (ID: 1050 | Field of Sunflowers.jpg | FILE | VISIBLE)
at com.adobe.drive.internal.biz.filesystem.FileSystemService.wrapException(FileSystemService.java:1645)
at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1695)
at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1668)
at com.adobe.drive.internal.biz.filesystem.FileSystemService.rename(FileSystemService.java:1003)
at com.adobe.drive.internal.ncomm.filesystem.RenameHandler.handleRequest(RenameHandler.java:68)
at com.adobe.drive.internal.ncomm.filesystem.AbstractHandler$1.call(AbstractHandler.java:204)
at com.adobe.drive.model.context.Context.run(Context.java:88)
at com.adobe.drive.internal.ncomm.filesystem.AbstractHandler.handleWithContext(AbstractHandler.java:200)
at com.adobe.drive.internal.ncomm.filesystem.AbstractHandler.handle(AbstractHandler.java:66)
at com.adobe.csi.internal.ncomm.NCommDelegate.execute(NCommDelegate.java:107)
at com.adobe.versioncue.internal.nativecomm.host.Host.execute(Host.java:200)
at com.adobe.versioncue.internal.nativecomm.host.ConnectionHandler.handleRequest(ConnectionHandler.java:162)
at com.adobe.versioncue.internal.nativecomm.host.ConnectionHandler.run(ConnectionHandler.java:81)
at java.lang.Thread.run(Thread.java:680)
Caused by: com.adobe.drive.data.model.DriveException: com.adobe.drive.data.manager.exception.PermissionDeniedException: Asset is unlocked (ID: 1050 | Field of Sunflowers.jpg | FILE | VISIBLE)
at com.adobe.drive.internal.data.manager.DataManager.convertException(DataManager.java:4617)
at com.adobe.drive.internal.data.manager.DataManager.moveAsset(DataManager.java:3809)
at com.adobe.drive.internal.biz.filesystem.FileSystemService$12.execute(FileSystemService.java:1020)
at com.adobe.drive.internal.biz.filesystem.FileSystemService$FSRunnable.run(FileSystemService.java:1825)
at com.adobe.drive.data.internal.persistence.PersistenceRunner.run(PersistenceRunner.java:119)
at com.adobe.drive.internal.biz.filesystem.FileSystemService.run(FileSystemService.java:1688)
... 12 more
Caused by: com.adobe.drive.data.manager.exception.PermissionDeniedException: Asset is unlocked (ID: 1050 | Field of Sunflowers.jpg | FILE | VISIBLE)
at com.adobe.drive.data.manager.exception.PermissionDeniedException.assetUnlocked(PermissionDeniedException.java:80)
at com.adobe.drive.data.manager.call.MoveApplication.checkProcessPreconditions(MoveApplication.java:56)
at com.adobe.drive.data.manager.call.Move.execute(Move.java:139)
at com.adobe.drive.internal.data.manager.DataManager.moveAsset(DataManager.java:3805)
... 16 more
Deleting files - an issue with 10.7.x
When a user tries to remove a file it doesn't have permission to, it first shows a confirmation dialog, then a login dialog, see the move issue. After entering the credentials it shows an error dialog which tells that the file cannot be deleted. This is already better than the move behavior, only the login dialog is not necessary.
Renaming files - an issue with 10.7.x
When a user tries to rename a file it doesn't have permission to, it first shows a login dialog, see the move issue. After entering the credentials it shows an error which tells that the file cannot be renamed.
North America
Europe, Middle East and Africa
Asia Pacific