keystone v3 authentication fails

I'm trying to get freezer to backup to a Swift, but currently it fails on authentication.
What I currently have is a fresh installation of an Openstack Swift and Keystone(mitaka release), done by official guides at http://docs.openstack.org/mitaka/install-guide-ubuntu/ , on clean Ubuntu 14.04. By itself if all works fine, I have a "demo" user that is capable of issuing a "swift stat" and creating/deleting containers and objects in swift.
I also have two client mashines with Windows Server 2012 and Ubuntu 14.04 acting as test clients with freezer installed. Both of them behaving in the same way, so it's not platform-specific.
When I try to backup something it responds with
"[*] Critical Error: Unauthorized. Check username/id, password, tenant name/id and user/tenant domain name/id."
Example command is "freezer-agent -F /home/user/test/ --backup-name testbackup1 --container backup1 --os-identity-api-version 3"
Example env is:
export OS_PROJECT_DOMAIN_NAME=default
export OS_USER_DOMAIN_NAME=default
export OS_PROJECT_NAME=demo
export OS_USERNAME=demo
export OS_PASSWORD=<some password>
export OS_AUTH_URL=http://controller:5000/v3
export OS_IDENTITY_API_VERSION=3

With the same env the "swift stat" from clients runs perfectly.

I was able to capture packets on controller with Wireshark, and from what I see:
when a "swift stat" is issued client is using "auth>scope>project>domain>name>default" hierarchy in json data;
when a freezer backup command is issued client is using "auth>scope>project>domain>id>default" hierarchy in json data.
They both trying to access /v3/auth/tokens, and everything else is the same. Only difference is "domain name" vs "domain id". Same goes for "user domain name" vs "user domain id" in json data.

As my understanding goes, this is the reason that breaks authentication.
Is this a problem with a freezer code(i.e. not yet supporting v3 authenticaton) or am I missing something?