That looks like a good start, but it would mean handling reauth at the client level (ie, because Connection knows how to reauth with either a Session or a url/username/password, but can’t with just a token)
From: Timur Alperovich <email address hidden>
Reply: Bug 1696236 <email address hidden>
Date: June 9, 2017 at 3:21:05 AM
To: <email address hidden> <email address hidden>
Subject: [Bug 1696236] Re: Document requesting + caching auth tokens
Agreed on the lack of documentation around this. I looked into the
client functions a little bit tonight and came up with the following:
I think the same approach works with the v2 authentication, but I
haven't tested that. I've only tried with v1 auth in the docker-swift
container, but the code for swiftclient.client.get_auth seems like it
supports v2 Keystone auth as well. Would this work for you to store the
storage URL and auth token in Redis or some other caching layer?
That looks like a good start, but it would mean handling reauth at the client level (ie, because Connection knows how to reauth with either a Session or a url/username/ password, but can’t with just a token)
From: Timur Alperovich <email address hidden>
Reply: Bug 1696236 <email address hidden>
Date: June 9, 2017 at 3:21:05 AM
To: <email address hidden> <email address hidden>
Subject: [Bug 1696236] Re: Document requesting + caching auth tokens
Agreed on the lack of documentation around this. I looked into the
client functions a little bit tonight and came up with the following:
>>> import swiftclient client. get_auth( 'http:// localhost: 32780/auth/ v1.0', 'test:tester', 'testing') client. Connection( preauthurl= storage_ url, preauthtoken= auth_token) container( 'test') 55304', u'x-openstack- request- id': u'tx1895dbebda3 e452dab2b8- 00593a485e' }
>>> storage_url, auth_token = swiftclient.
>>> conn = swiftclient.
>>> conn.head_
{[...] u'x-timestamp': u'1496991830.
I think the same approach works with the v2 authentication, but I client. get_auth seems like it
haven't tested that. I've only tried with v1 auth in the docker-swift
container, but the code for swiftclient.
supports v2 Keystone auth as well. Would this work for you to store the
storage URL and auth token in Redis or some other caching layer?
-- /bugs.launchpad .net/bugs/ 1696236
You received this bug notification because you are subscribed to the bug
report.
https:/
Title:
Document requesting + caching auth tokens
To manage notifications about this bug go to: /bugs.launchpad .net/python- swiftclient/ +bug/1696236/ +subscriptions /twitter. com/wolever
https:/
--
https:/
(416) 906-0403
B230230D