directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitry Bedrin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DIRKRB-659) Support authentication with NT-ENTERPRISE principal names
Date Wed, 21 Mar 2018 19:29:00 GMT

     [ https://issues.apache.org/jira/browse/DIRKRB-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dmitry Bedrin updated DIRKRB-659:
---------------------------------
    Fix Version/s: 1.1.1

> 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
>            Priority: Major
>              Labels: patch, windows
>             Fix For: 1.1.1
>
>         Attachments: DIRKRB_659__Support_authentication_with_NT_ENTERPRISE_principal_names.patch
>
>   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
(v7.6.3#76005)

Mime
View raw message