You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Dmitry Bedrin (JIRA)" <ji...@apache.org> on 2017/09/27 11:33:00 UTC

[jira] [Comment Edited] (DIRKRB-659) Support authentication with NT-ENTERPRISE principal names

    [ https://issues.apache.org/jira/browse/DIRKRB-659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16182404#comment-16182404 ] 

Dmitry Bedrin edited comment on DIRKRB-659 at 9/27/17 11:32 AM:
----------------------------------------------------------------

[~drankye], absolutely! I should have done it in the first place - I've updated the ticket


was (Author: dmitry.bedrin@gmail.com):
[~drankye] should have done it in the first place - I've updated the ticket

> Support authentication with NT-ENTERPRISE principal names
> ---------------------------------------------------------
>
>                 Key: DIRKRB-659
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-659
>             Project: Directory Kerberos
>          Issue Type: New Feature
>    Affects Versions: 1.0.1
>            Reporter: Dmitry Bedrin
>   Original Estimate: 24h
>  Remaining Estimate: 24h
>
> Apache Kerby currently doesn't support authentication using NT-ENTERPRISE principal names.
> See https://tools.ietf.org/html/rfc6806.html for details
> _KrbClientBase_ provides a method for requesting _TGT_ with arbitrary _KOptions_
>     public TgtTicket requestTgt(KOptions requestOptions) throws KrbException
> However even if I set KrbOption.AS_ENTERPRISE_PN and use username like "username@dns.domain.name" Kerby Client will treat the dns.domain.name as a realm name despite the AS_ENTERPRISE_PN  setting



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)