Return-Path: X-Original-To: apmail-directory-dev-archive@www.apache.org Delivered-To: apmail-directory-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 607D517EFB for ; Wed, 27 May 2015 08:17:18 +0000 (UTC) Received: (qmail 10384 invoked by uid 500); 27 May 2015 08:17:17 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 10314 invoked by uid 500); 27 May 2015 08:17:17 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 9980 invoked by uid 99); 27 May 2015 08:17:17 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 27 May 2015 08:17:17 +0000 Date: Wed, 27 May 2015 08:17:17 +0000 (UTC) From: "Kai Zheng (JIRA)" To: dev@directory.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DIRKRB-126) Implementing TokenPreauth mechanism MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DIRKRB-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14560612#comment-14560612 ] Kai Zheng commented on DIRKRB-126: ---------------------------------- Thanks Jiajia for the great work implementing the token mechanism! The patch looks awesome to me. +1 > Implementing TokenPreauth mechanism > ----------------------------------- > > Key: DIRKRB-126 > URL: https://issues.apache.org/jira/browse/DIRKRB-126 > Project: Directory Kerberos > Issue Type: Sub-task > Reporter: Kai Zheng > Assignee: Jiajia Li > Attachments: DIRKRB-126-v1.patch > > > This is to implement token-preauth mechanism defined in token-preauth draft. Ref. docs/token-preauth.pdf. The result work is only for experimental usage and could be promoted as production usage when the draft is finally passed. Currently we're collaborating with MIT Kerberos team discussing thru the spec but due to the low priority it's running very slow. By this implementation and possible POCs good experience can be obtained as feedback to refine the draft. -- This message was sent by Atlassian JIRA (v6.3.4#6332)