Ask Your Question
0

Problems when changing port 8080 to 443 on Proxy

asked 2012-08-08 19:02:17 -0500

jorhen111 gravatar image

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
edit retag flag offensive close merge delete

5 answers

Sort by » oldest newest most voted
0

answered 2012-08-08 19:16:36 -0500

notmyname gravatar image

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).

edit flag offensive delete link more
0

answered 2012-08-08 19:28:16 -0500

jorhen111 gravatar image

We are using the Cyberduck client.

edit flag offensive delete link more
0

answered 2012-08-10 17:55:40 -0500

tonytkdk gravatar image

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

edit flag offensive delete link more
0

answered 2012-08-12 14:59:34 -0500

jorhen111 gravatar image

We are using Swauth.

edit flag offensive delete link more
0

answered 2012-08-14 04:30:18 -0500

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

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-08-08 19:02:17 -0500

Seen: 314 times

Last updated: Aug 14 '12