Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

mfh2

208 Posts

4622

November 1st, 2010 08:00

Atmos EE 1.3.2 REST/CIFS Interface

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 /apache.

Thanks for any input.

JasonCwik

281 Posts

November 5th, 2010 07:00

Hi Mike,

Sorry, I had the grant wrong.  Change it to this:

acl.addGrant(new Grant(Grantee.OTHER, Permission.FULL_CONTROL));

Anonymous

5 Practitioner

 • 

274.2K Posts

November 3rd, 2010 13:00

Hi,

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?


Thanks,
Vinay

mfh2

208 Posts

November 3rd, 2010 14:00

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

Regards,

Mike

JasonCwik

281 Posts

November 4th, 2010 16:00

Mike,

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.

mfh2

208 Posts

November 5th, 2010 05:00

 
 
 
 
 
 
 
 
 
 
 
 

  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)

mfh2

208 Posts

November 5th, 2010 09:00

Hi Jason -

Thank you very much, that worked!  We can now access the namespace-written content through CIFS.

Best Regards,

Mike

View More

View All

No Events found!

Top