gswauth: Fix 403 being returned instead of 401

- 401(Unauthorized) is to be returned when user credentials are
  wrong where as 403(Forbidden) is to be returned when user
  credentials are correct but the user doesn't have the priveleges
  to carry out the operation.

- Also error messages displayed when using swauth-* command line
  utilities have been updated.

Change-Id: I485786896ad14d3263f4325d1857cacc93adab96
Signed-off-by: Prashanth Pai <ppai@redhat.com>
Reviewed-on: http://review.gluster.org/6336
Reviewed-by: Luis Pabon <lpabon@redhat.com>
Tested-by: Luis Pabon <lpabon@redhat.com>

1 files changed, 8 insertions, 1 deletions

diff --git a/gluster/swift/common/middleware/gswauth/bin/swauth-set-account-service b/gluster/swift/common/middleware/gswauth/bin/swauth-set-account-service
index b0bed38..41a33d2 100755
--- a/gluster/swift/common/middleware/gswauth/bin/swauth-set-account-service
+++ b/gluster/swift/common/middleware/gswauth/bin/swauth-set-account-service
@@ -70,4 +70,11 @@ Example: %prog -K swauthkey test storage local http://127.0.0.1:8080/v1/AUTH_018
     conn.send(body)
     resp = conn.getresponse()
     if resp.status // 100 != 2:
-        exit('Service set failed: %s %s' % (resp.status, resp.reason))
+        if resp.status == 401:
+            exit('Service set failed: %s %s: Invalid user/key provided' %
+                (resp.status, resp.reason))
+        elif resp.status == 403:
+            exit('Service set failed: %s %s: Insufficient priveleges' %
+                (resp.status, resp.reason))
+        else:
+            exit('Service set failed: %s %s' % (resp.status, resp.reason))