OpenStack Object Storage (swift)

SWauth issues in OpenStack Swift

Asked by Konark Gill

I have configured my Openstack swift for multi node installation. it was working fine. I wanted to add SWAUTH on top of it to
use S3 APIs.

I have installed swauth from github.

1. https://github.com/gholt/swauth.git.
2. Ran command sudo python setup.py install.
3. Made changes to my proxy-server.conf. It looks like this now.

[DEFAULT]
cert_file = /etc/swift/cert.crt
key_file = /etc/swift/cert.key
bind_port = 8080
workers = 8
user = swift

[pipeline:main]
pipeline = catch_errors cache swauth proxy-server

[app:proxy-server]
use = egg:swift#proxy
allow_account_management = true

[filter:swauth]
use:egg:swauth#swauth
set log_name = swauth
super_admin_key = swauthkey
default_swift_cluster = local#https://128.111.55.19:8080/v1

[filter:cache]
use = egg:swift#memcache
memcache_servers = 128.111.55.19:11211

[filter:catch_errors]
use = egg:swift#catch_errors

4. After this i run the commnad $swift-init proxy reload. It works fine.
5. I run the command swauth-prep -K swauthkey.

The proxy server is stuck no response from it , no error nothing just stuck.

Please help me out as to wht could be the prob.

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Object Storage (swift) Edit question
Assignee:
No assignee Edit question
Solved by:
Marcelo Martins
Solved:
Last query:
Last reply:
Revision history for this message
Best Marcelo Martins (btorch) said : 		#1

Hi Konark,

Have you tried specifying the AUTH_URL to the command ? The default is HTTP and since you have HTTPS setup it will probably just hang.

Try: swauth-prep -K swauthkey -A https://127.0.0.1:8080/auth/

Revision history for this message
Konark Gill (konark-gill) said : 		#2

Thanks Marcelo Martins, that solved my question.

Revision history for this message
Konark Gill (konark-gill) said : 		#3

Thanks a lot Marcelo

Revision history for this message
Kyle (472676920-9) said : 		#4

How to setup https?

Revision history for this message
John Dickinson (notmyname) said : 		#5

if the proxy server has the cert_file and key_file options defined, then it will use ssl

(however, I must point out that using ssl dorectly to the proxy is only a good idea for limited testing. Please use a load balancer or reverse proxy to terminate your ssl connections before the proxy.)

Revision history for this message
Kyle (472676920-9) said : 		#6

I've defined cer_file and key_file in proxy-server.conf.
[DEFAULT]
cert_file = /etc/swift/cert.crt
key_file = /etc/swift/cert.key
bind_port = 8080
workers = 8
user = swift

my situation is just like Konarks'.According to what Marceb said,I need to setup https to solve this problm.But I couldn't find any way to setup https.

please tell me what command I should input to solve this problem.