swauth account:user design

asked 2011-08-08 17:57:11 -0600

I am a bit confused when it comes to the design of swauth and swift with regards to the need for an account and a user. What is the point of having both?

When I follow the instructions to create a admin account a system:root with the -a flag everything seems to work fine in st/Cyberduck but when I add an account without the -a flag I can not HEAD the account and get a forbidden. Are there extra steps needed to authorize the account that I am missing?

It seems waiting for Keystone to integrate into outside authorization/authentication sources seems to be the best plan, will this totally replace swauth?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2011-08-08 18:15:16 -0600

notmyname gravatar image

An account added without the "-a" flag needs to be explicitly given permission to access certain containers (with the X-Container-Read and X-Container-Write headers).


edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2011-08-08 17:57:11 -0600

Seen: 21 times

Last updated: Aug 08 '11