OpenStack Object Storage (swift)

Problems when changing port 8080 to 443 on Proxy

Asked by Jorge Henrique

Hi all,

    We have setup a swift cloud initially to a port 8080. Then we added some users, containers and objects. Everything was working fine. However, after changing the service to work on the port 443, the users that were using the port 8080 cannot log in. If we create a new user, she can log on the port 443, but the old ones cannot.

   Is there any way to let old users log in in the proxy by means of port 443 ?

              thanks,

        Jorge

Question information

Language:
English Edit question
Status:
Answered
For:
OpenStack Object Storage (swift) Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
John Dickinson (notmyname) said : 		#1

What client app are you using?

My initial guess is that your auth endpoints for the old users hasn't been updated to return :433 in the storage URL (therefore the client is trying to still connect to :8080).

Revision history for this message
Jorge Henrique (jorhen111) said : 		#2

We are using the Cyberduck client.

Revision history for this message
Hugo Kou (tonytkdk) said : 		#3

In my consideration is that you can check the returned proxy endpoint from keystone with different users(old/new one)

Revision history for this message
Jorge Henrique (jorhen111) said : 		#4

We are using Swauth.

Revision history for this message
yaguang wang (ywang19) said : 		#5

you could try following steps to associate user to new endpoint, just reminder, below steps will remove original user and create one new one.

i) # delete existed user and account
a. Swauth-delete-user –K <auth-key> –A http://<ip>:8080/auth <account> <user>
b. Swauth-delete-account –A http://<ip>:8080/auth/v1.0 -K <auth-key> <account>
ii) # restart proxy server
a. Swift-init proxy restart
b. service memcached restat
iii) # add new account
a. Swauth-prep –K <auth-key> –A http://<ip>:443/auth/
b. Swauth-add-user –K <auth-key> –A http://<ip>:443/auth/ -a <account> <user> <password>
iv) # verify connectivity
a. curl -k -v -H "X-Auth-User: <account>:<user>" -H "X-Auth-Key: <password> " http://<ip>:443/auth/v1.0

Can you help with this problem?

Provide an answer of your own, or ask Jorge Henrique for more information if necessary.

To post a message you must log in.