We're testing Atmos using the v1.3.2 Evaluation Edition (Atmos-in-a-box) available from this developer portal. We are particularly interested in coordination between the REST and CIFS interfaces. We'd like to ingest data through REST yet make it visible to clients through the CIFS namespace interface.
We are able to write and read files directly through the CIFS interface without issue. However, when we use the Ashish's Atmos Browser to store an object vvia REST we can see the file through CIFS using Windows Explorer but we always get a permissions error when trying to open the file via CIFS.
One interesting bit of information is that the files written using CIFS show object metadata uid/gid of 99/99 and the REST-written objects show uid/gid properties of <username>/apache.
Thanks for any input.
Solved! Go to Solution.
Atmos doesn't support this as user authentication for REST is different than that of CIFS. Is there a compelling use case for this functionality?
Hi Vinay -
Thank you for responding. Just to clarify, you're stating that:
- objects written using the REST API using the /rest/namespace endpoint cannot be accessed via the CIFS interface
- in order for a file to be accessible from the CIFS interface, it must be written to the Atmos system via CIFS
When you create your object through the REST interface, you can set the x-emc-groupacl public=FULL_CONTROL. That should allow the file to be read through CIFS.
Hi Jason -Thank you for the reponse. We've tested the following code (using the Java bindings):EsuApi cesu = new EsuRestApiApache("host", 80, "user", "sharedSecret");UploadHelper helper = new UploadHelper(cesu);Acl acl = new Acl();acl.addGrant(new Grant(new Grantee("public", Grantee.GRANT_TYPE.GROUP), Permission.FULL_CONTROL));ObjectId id = helper.createObjectOnPath(new ObjectPath("/test/file.txt"), new File("/root/file.txt"), acl, null);System.out.println(cesu.getAcl(id).toString());The output from this snippet is "[user=FULL_CONTROL, other=NONE]".Unfortunately, the file is still not readable via CIFS. Looking through the Java bindings source,it appears that the correct HTTP header is being sent to Atmos.Are we doing something wrong?Best Regards,Mike
Message was edited by: mfh (for formatting)