Randy Black <[email protected]> writes: > Doing something stooopid. Please point it out: > > authfile; > > [swift] > backend-login:<tenant>:<user> > backend-password:<password> > storage-url: swiftks://<host>:<port>/<region>/<container> ## container > does exist, created with swift cli > > > mkfs command; > > mkfs.s3ql --debug all --authfile .s3ql_auth --plain --cachedir /.s3ql_cache > swiftks://<host>:<port>/<region>/<container> > > it still prompts for creds??
Does it work if you temporarily put just one entry in your authfile, and set the storage-url to swiftks:// (i.e., don't include host etc)? > I get a 401 and then a 'discard'. Note: I can see a valid token given by > my auth server on the backend while tailing the logs. Please try this patch: https://bitbucket.org/nikratio/s3ql/commits/3f008146e9e192a0bb424bc5da99132fb1e3c349 Best, -Nikolaus -- GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F »Time flies like an arrow, fruit flies like a Banana.« -- You received this message because you are subscribed to the Google Groups "s3ql" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
