[Cyberduck-trac] [Cyberduck] #5735: Swift authentication fails for installations using "swauth"

[Cyberduck]

#5735: Swift authentication fails for installations using "swauth"
---------------------------+-------------------------
 Reporter:  devcamcar      |         Owner:  dkocher
     Type:  defect         |        Status:  reopened
 Priority:  normal         |     Milestone:  4.2
Component:  openstack      |       Version:  3.8.1
 Severity:  major          |    Resolution:
 Keywords:  swift, swauth  |  Architecture:
 Platform:                 |
---------------------------+-------------------------
Changes (by dkocher):

 * milestone:  4.1 => 4.2


Comment:

 Replying to [comment:10 rpedde]:
 > I think this could potentially be an ongoing issue as other
 authentication backends are implemented for swift.  It's very possible
 that any new auth backend could use a different auth endpoint.  Until
 swauth (AFAIK), swift never even tried to perform any auth functions,
 relying on an external auth system and external token validation.  I guess
 what I'm saying is that I don't feel that the auth URI is part of the
 swift protocol spec, and its location is completely arbitrary, and may
 vary on a per-provider basis.
 >
 > I agree that it would be helpful to have a completely free-form auth
 URI, or at least the option to enter one.
 >
 > Certainly not a criticism though, I do appreciate all your efforts.

 Thanks for your insights on this issue. If we want to support arbitrary
 authentication context paths, we will have to introduce another login
 prompt that allows to specify the path. But that would be quite a
 cumbersome login process for the average user.

-- 
Ticket URL: <http://trac.cyberduck.ch/ticket/5735#comment:11>
Cyberduck <http://cyberduck.ch>
Open source FTP, SFTP, WebDAV, Cloud Files, Google Docs & Amazon S3 Browser for Mac & Windows.