On Jun 20, 2012, at 11:02 AM, Victor Rodionov wrote:
>
> Also, I want ask do you think it's good idea to store object ACL in object
> metadata?
I'd suggest looking at container-level ACLs rather than object-level. But
either way, the data does need to be stored in the metadata in swift itself
Hello
My implementation need only "remote user" header from authorization system with
user name (comma separated list of username (roles)) or put key REMOTE_USER to
WSGI env. So it will work ok with tempauth, because it add REMOTE_USER to env.
For keystone no much changes will be needed.
Unfor
Have you worked with Fujita Tomonori? If not, you might consider collaborating
on https://github.com/fujita/swift3
On Jun 20, 2012, at 9:38 AM, Victor Rodionov wrote:
> Hello
>
> I have working implementation of S3 like ACL API for Swift, for this changes
> I need to store ACL on object and c
Yes, this could be good for swift.
ACLs in swift do need to be stored in swift (for scale reasons), but their
implementation is dependent on the particular auth system that you are using.
The auth middleware is responsible for determining if a request is granted
access to a particular swift ent
Hello
I have working implementation of S3 like ACL API for Swift, for this
changes I need to store ACL on object and container server, then I need
to change container and object servers code.
So my question, if this changes will be interesting for Swift community
or no?
Thanks,
Victor
___
5 matches
Mail list logo
