The auth system and how you organize the data are separate. You can certainly store all objects in one account (although I'd recommend you spread the objects across many containers). You could also not use any auth at all (by removing tempauth or keystone from the pipeline in the proxy server config), although only you know if that's a good idea or not.
--John On Aug 22, 2013, at 6:44 PM, pangj <pa...@laposte.net> wrote: > Hi, > > Given the case that we just want to store objects in Swift, but don't want > the auth process (all the storage devices are in intranet). > > Swift has a tempauth filter. Can I store all objects under the system/root > account by tempauth? Or is there any better way? > > Thanks. > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : openstack@lists.openstack.org > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
