Hi Porunov. Unfortunately, I'm not a swift expert, however I can provide you my own experience. There is multiple solutions I think.

The best one is to replace keystone by another authentication middleware such as ldap, radius, or your own written middleware.

The next two options are not recommended in production but runs swift independently to other services :

You can use the swift internal tempauth authentication middleware, however, this is not scalable and if you have more than one proxy, you must route all request related to an authentication token to the same proxy because a token generated on one proxy is unknown on the other one and will be rejected.

The last solution is to not use any authentication by just removing all authentication related plugins declared in the pipeline. This works well and is scalable but is far less secure. But who knows, it can fit your own needs depending on how much you network is secured and who can generate an http request to your proxys.