There are 2 tokens involved. One is the user token and other is the service token. Easy way to debug is to hit keystone directly and find out which token is failing. Since all your services are fine, most probably the service token is the one that is failing.

Service user/ service tenant/ service password are in the swift.conf ( middleware configuration ). Check them

Hi,

Swift.conf only contain the below details. As per the docs there is no middleware configuration in the swift.conf.

========================================================================= [swift-hash]

random unique string that can never change (DO NOT LOSE)

swift_hash_path_suffix = fLIbertYgibbitZ

Which version  have you migrated from?  Once upon a time swift used to use swiauth which is different from keystone auth.  Was it using swauth before?

Don't you have something like this in your swfit configuration file?   If you have this, then there is a username/password defiend that needs to be validated. 

[filter:authtoken]
paste.filter_factory = keystoneclient.middleware.auth_token:filter_factory

# Delaying the auth decision is required to support token-less
# usage for anonymous referrers ('.r:*').
delay_auth_decision = true

# cache directory for signing certificate
signing_dir = /etc/swift/keystone-signing

# auth_* settings refer to the Keystone server
auth_protocol = http
auth_host = <keystoen_host>
auth_port = 35357

# the service tenant and swift username and password created in Keystone
admin_tenant_name = service
admin_user = swift
admin_password = swift