Return-Path: X-Original-To: apmail-accumulo-commits-archive@www.apache.org Delivered-To: apmail-accumulo-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3D30FF451 for ; Tue, 14 May 2013 00:58:16 +0000 (UTC) Received: (qmail 65940 invoked by uid 500); 13 May 2013 23:57:42 -0000 Delivered-To: apmail-accumulo-commits-archive@accumulo.apache.org Received: (qmail 65917 invoked by uid 500); 13 May 2013 23:57:42 -0000 Mailing-List: contact commits-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@accumulo.apache.org Delivered-To: mailing list commits@accumulo.apache.org Received: (qmail 65910 invoked by uid 99); 13 May 2013 23:57:42 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 23:57:42 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 13 May 2013 23:57:40 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 29ADC2388A32; Mon, 13 May 2013 23:57:19 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1482154 - in /accumulo/trunk: ./ docs/src/main/latex/accumulo_user_manual/chapters/security.tex Date: Mon, 13 May 2013 23:57:19 -0000 To: commits@accumulo.apache.org From: vines@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20130513235719.29ADC2388A32@eris.apache.org> X-Virus-Checked: Checked by ClamAV on apache.org Author: vines Date: Mon May 13 23:57:18 2013 New Revision: 1482154 URL: http://svn.apache.org/r1482154 Log: ACCUMULO-992 - Forgot to save a file before committing Modified: accumulo/trunk/ (props changed) accumulo/trunk/docs/src/main/latex/accumulo_user_manual/chapters/security.tex Propchange: accumulo/trunk/ ------------------------------------------------------------------------------ Merged /accumulo/branches/1.5:r1482153 Modified: accumulo/trunk/docs/src/main/latex/accumulo_user_manual/chapters/security.tex URL: http://svn.apache.org/viewvc/accumulo/trunk/docs/src/main/latex/accumulo_user_manual/chapters/security.tex?rev=1482154&r1=1482153&r2=1482154&view=diff ============================================================================== --- accumulo/trunk/docs/src/main/latex/accumulo_user_manual/chapters/security.tex (original) +++ accumulo/trunk/docs/src/main/latex/accumulo_user_manual/chapters/security.tex Mon May 13 23:57:18 2013 @@ -139,12 +139,15 @@ deprecation cycle. Authentication simply handles the ability for a user to verify their integrity. A combination of principal and authentication token are used to verify a user is who they say they are. An authentication token should be constructed, either directly through it's constructor, but it is -advised to use the init(Property) method to populate an authentication token. Once a user is -authenticated by the Authenticator, the user has access to the other actions within Accumulo. All -actions in Accumulo are ACLed, and this ACL check is handled by the Permission Handler. This is what -manages all of the permissions, which are divided in system and per table level. From there, if a -user is doing an action which requires authorizations, the Authorizor is queried to determine what -authorizations the user has. +advised to use the init(Property) method to populate an authentication token. It is expected that a +user knows what the appropriate token to use for their system is. The default token is +PasswordToken. + +Once a user is authenticated by the Authenticator, the user has access to the other actions within +Accumulo. All actions in Accumulo are ACLed, and this ACL check is handled by the Permission +Handler. This is what manages all of the permissions, which are divided in system and per table +level. From there, if a user is doing an action which requires authorizations, the Authorizor is +queried to determine what authorizations the user has. This setup allows a variety of different mechanisms to be used for handling different aspects of Accumulo's security. A system like Kerberos can be used for authentication, then a system like LDAP