Almost all OpenStack Swift docs mention that TempAuth is a solution only for a test environment other than prod (however it is fully functional). <br> The main reason not to use this approach is that user loans are stored in a simple configuration file, which reduces the overall security of the object store.
On the other hand, if the application uses the internal storage of objects (therefore, it stores only files in the internal infrastructure), and authentication and authorization are provided by the application itself, it seems that this approach may be suitable for use in production.
Could you share other disadvantages of using TempAuth in the prod environment, given that the object store is internal (or add additional arguments that match :))?
source share