manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-1103) Add Kerberos support for all connectors that currently use NTLM
Date Wed, 30 Jan 2019 17:54:00 GMT

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

Michael Osipov commented on CONNECTORS-1103:
--------------------------------------------

Nice you are citing my Sorceforge projects ;-) I plan add this too with an implicit {{GSSCredential}}
but this should actually necessary because you can leverage a {{Subject}} insance with the
private credentials and the {{doAs()}} to achieve the same. The internals of HttpClient would
run in the scope of the explicit credential.

> Add Kerberos support for all connectors that currently use NTLM
> ---------------------------------------------------------------
>
>                 Key: CONNECTORS-1103
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1103
>             Project: ManifoldCF
>          Issue Type: Improvement
>          Components: FileNet connector, LiveLink connector, RSS connector, SharePoint
connector, Web connector
>    Affects Versions: ManifoldCF 1.7.2
>            Reporter: Karl Wright
>            Assignee: Karl Wright
>            Priority: Major
>             Fix For: ManifoldCF next
>
>
> You can solve your local ticket store by using LoginContext and appropriate keytabs.
Obtain the GSSCredential and go. Every connection instance can act independently. Regardless
of the OS.
> If you cache the subject issued by the aforementioned LoginContext, you can always say:
GssCredential#getRemainingLifetime or invoke a fresh LoginContext as you think fit.
> Unfortunately, HTTPClient does not support direct use of GSSCredential and always assumes
implicit credential. Fortunately, there are several ways to solve that problem too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message