diff options
author | Chetan Risbud <crisbud@redhat.com> | 2014-02-06 16:04:40 +0530 |
---|---|---|
committer | Luis Pabon <lpabon@redhat.com> | 2014-03-14 11:56:15 -0700 |
commit | 2505d8281593730d8b31794d0fe8132417c34a48 (patch) | |
tree | 6179930dffe024413f7acb340965b30a71d2754a /doc | |
parent | 73aa6e788398e0c25e6dd527f968f5ce4b433e79 (diff) |
Functional tests for SwiftKerbAuth filter.
This provides an infrastructure for swiftkerbauth
related functional test cases.
More test cases will be added later.
Added a section in swiftkerbauth guide about how to run
functional tests.
test/functional_auth/swiftkerbauth
----------------------------------
A new authentication filter related functional
tests and configuration to reside here.
The configuration would help setup the
environment. All the generic functional tests
should run fine with PASSIVE mode of swiftkerbatuh.
Please refere to swiftkerbatuh documentation for
ACTIVE/PASSIVE mode of working.
swiftkerbauth/test_swkrbath_active.py
-------------------------------------
This file has all the testcases of active mode of
swiftkerbauth. More test cases to be added later.
SwiftKerbAuth related test cases are meant to run
on the setup where SwiftKerbAuth is setup and
installed.
Change-Id: Ibc2a3945f5c9b6714475fcec0ee9d153debb48e3
Signed-off-by: Chetan Risbud <crisbud@redhat.com>
Reviewed-on: http://review.gluster.org/6925
Reviewed-by: Luis Pabon <lpabon@redhat.com>
Tested-by: Luis Pabon <lpabon@redhat.com>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/markdown/swiftkerbauth/swiftkerbauth_guide.md | 34 |
1 files changed, 30 insertions, 4 deletions
diff --git a/doc/markdown/swiftkerbauth/swiftkerbauth_guide.md b/doc/markdown/swiftkerbauth/swiftkerbauth_guide.md index 12845a6..5da1827 100644 --- a/doc/markdown/swiftkerbauth/swiftkerbauth_guide.md +++ b/doc/markdown/swiftkerbauth/swiftkerbauth_guide.md @@ -1,10 +1,11 @@ #swiftkerbauth -* [Installing Kerberos module for Apache on IPA client] (#httpd-kerb-install) -* [Creating HTTP Service Principal on IPA server] (#http-principal) -* [Installing and configuring swiftkerbauth on IPA client] (#install-swiftkerbauth) +* [Installing Kerberos module for Apache] (#httpd-kerb-install) +* [Creating HTTP Service Principal] (#http-principal) +* [Installing and configuring swiftkerbauth] (#install-swiftkerbauth) * [Using swiftkerbauth] (#use-swiftkerbauth) * [Configurable Parameters] (#config-swiftkerbauth) +* [Functional tests] (#swfunctest) <a name="httpd-kerb-install" /> ## Installing Kerberos module for Apache on IPA client @@ -487,5 +488,30 @@ Default value: passive #### realm_name This is applicable only when the auth_method=passive. This option specifies -realm name if RHS server belongs to more than one realm and realm name is not +realm name if storage server belongs to more than one realm and realm name is not part of the username specified in X-Auth-User header. + +<a name="swfunctest" /> +##Functional tests for SwiftkerbAuth + +Functional tests to be run on the storage node after SwiftKerbAuth is setup using +either IPA server or Windows AD. The gluster-swift/doc/markdown/swiftkerbauth +directory contains the SwiftkerbAuth setup documents. There are two modes of +working with SwiftKerbAuth. 'PASSIVE' mode indicates the client is outside the +domain configured using SwiftKerbAuth. Client provides the 'Username' and +'Password' while invoking a command. SwiftKerbAuth auth filter code then +would get the ticket granting ticket from AD server or IPA server. +In 'ACTIVE' mode of SwiftKerbAuth, User is already logged into storage node using +its kerberos credentials. That user is authenticated across AD/IPA server. + +In PASSIVE mode all the generic functional tests are run. ACTIVE mode has a +different way of acquiring Ticket Granting Ticket. And hence the different +framework of functional tests there. + +The accounts, users, passwords must be prepared on AD/IPA server as per +mentioned in test/functional_auth/swiftkerbauth/conf/test.conf + +Command to invoke SwiftKerbAuth functional tests is +> $tox -e swfunctest + +This would run both ACTIVE and PASSIVE mode functional test cases. |