From caa8a4ea50734378e7e19f70b39a837c58e9d229 Mon Sep 17 00:00:00 2001 From: Jeff Darcy Date: Thu, 17 Apr 2014 23:21:05 +0000 Subject: rpc/auth: allow SSL identity to be used for authorization Access to a volume is now controlled by the following options, based on whether SSL is enabled or not. * server.ssl-allow: get identity from certificate, no password needed * auth.allow: get identity and matching password from command line It is not possible to allow both simultaneously, since the connection itself is either using SSL or it isn't. Change-Id: I5a5be66520f56778563d62f4b3ab35c66cc41ac0 BUG: 1114604 Signed-off-by: Jeff Darcy Reviewed-on: http://review.gluster.org/3695 Tested-by: Gluster Build System Reviewed-by: Vijay Bellur --- tests/bugs/bug-873367.t | 1 + 1 file changed, 1 insertion(+) (limited to 'tests/bugs') diff --git a/tests/bugs/bug-873367.t b/tests/bugs/bug-873367.t index 56c2d30542f..17be3572b2f 100755 --- a/tests/bugs/bug-873367.t +++ b/tests/bugs/bug-873367.t @@ -24,6 +24,7 @@ ln $SSL_CERT $SSL_CA TEST $CLI volume create $V0 $H0:$B0/1 TEST $CLI volume set $V0 server.ssl on TEST $CLI volume set $V0 client.ssl on +TEST $CLI volume set $V0 auth.ssl-allow Anyone TEST $CLI volume start $V0 TEST glusterfs --volfile-server=$H0 --volfile-id=$V0 $M0 -- cgit