You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Jiajia Li (JIRA)" <ji...@apache.org> on 2015/07/24 08:10:04 UTC
[jira] [Commented] (DIRKRB-374) An end to end test for the token
mechanism
[ https://issues.apache.org/jira/browse/DIRKRB-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14639988#comment-14639988 ]
Jiajia Li commented on DIRKRB-374:
----------------------------------
Refine the patch based on v2 and committed, thanks for Kai's help.
commit f12cd5540eab5f445588d50285f615f7f985d64d
Author: plusplusjiajia <ji...@intel.com>
Date: Fri Jul 24 14:13:14 2015 +0800
DIRKRB-374 An end to end test for the token mechanism.
> An end to end test for the token mechanism
> ------------------------------------------
>
> Key: DIRKRB-374
> URL: https://issues.apache.org/jira/browse/DIRKRB-374
> Project: Directory Kerberos
> Issue Type: Test
> Reporter: Kai Zheng
> Assignee: Jiajia Li
> Fix For: 1.0.0-RC1
>
> Attachments: DIRKRB-374-v1.patch, DIRKRB-374-v2.patch
>
>
> We have implemented end to end tests for classical Kerberos protocol, like password, ticket cache and keytab authentication or login. Kerby also supports a novel token mechanism, using a JWT token to authenticate or login. We need an integration test for the support. It should also serve for a sample purpose illustrating how to use it from user's point of view.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)