swauth account:user design
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?