What I'm saying is that if you want to provide Create, Read, Update, Delete access to your data path in ECS via Active Directory, you can use the secret key self-service feature via the management API.  This is specific to S3 and not going to work if you're using Swift.  When I say data path I mean S3, Swift, Atmos, CAS protocols.  When I say management API I mean using the ECS management API ([URL] within which provides the secret key self-service methods.  The work flow would be:  1.) AD user authenticates into ECS management API ([URL] 2.) Using the token obtained above, call the secret key self-service API to get/generate an S3 secret key ([URL] 3.) Log out of the management API to discard token. 4.) Using the secret key obtained in step 2, perform CRUD operations via S3.  At this point, if you still have questions, I suggest we jump on a quick WebEx to discuss further.  Thanks,  Ben
Can any one please give a step by step with technical reasons how to configure Swift Protocol with ECS.  Same also with S3 protocol  Thanks in advance
How to configure Swift protocol with ECS