Since the bug is in creating an access token by filepath I did a work around by looking up the object ID.  It adds an extra service call, but at least it works.  ObjectInfo oi = atmosApi.getObjectInfo(new ObjectPath(path)); CreateAccessTokenRequest request = new CreateAccessTokenRequest(); request.setIdentifier(oi.getObjectId());
Using the Java API 2.1.3 I can create, edit and delete files and directories with spaces in them, but I can't create an access token.  I'm using the namespace interface.  I get Atmos error code 1002: One or more arguments in the request were invalid. This comes back from an http 400 from Atmos.  For example I have two files uploaded: /foo/bang/test_upload.txt /foo/bang/test upload.txt I uploaded both files via the Java API, I can also view them in the Atmos Chrome extension.  When I call createAccessToken on each of them ( using the same Policy and no ACL) I get the 1002 error on the one with the space in the name.  Is there a problem in the atmos-java project or with Atmos itself?
Java API createAccessToken file name restrictions