Open timss opened 7 years ago
Hello !
This is not yet available in SVFS but should be relatively easy to implement since as you noted the upstream library has support for this.
I'll give it a shot soon.
Great, thanks!
Is this issue still open ? I have the same behavior on the client side. Can't check what's going on in the keystone, I do not have access but it is a V3 as well. I can access through swift client but mounting with svfs fails.
Hi, and thanks for creating SVFS :)
Context
Steps to reproduce this issue :
mount
command.Results you expected :
Containers in project, or if specified, a container, is to be mounted at mountpoint (see debug).
Results you observed :
Mount failed due to problems authenticating with Keystone, which expects a domain to be specified using v3 API.
Debug log :
SVFS debug:
Keystone log: (removed some verbose datetime/req output)
Additional information :
It seems that SVFS supports identity v3, but I can't find a way to specify domain(s).
I have no experience with Go, but digging a bit into the code it seems that xlucas/swift (and its upstream project) is the library used for Swift authentication. This library does seem to support v3 and with domains (see code), but is this implemented (as an option) in SVFS?
In a multidomain setup, you'd typically have to define both the domain of the user (
$OS_USER_DOMAIN_NAME
) and the domain of the project ($OS_PROJECT_DOMAIN_NAME
) for Keystone to know which domain (and driver) to use. For instance:Would it be possibly to do or add this to SVFS?