[
https://issues.apache.org/jira/browse/CONNECTORS-664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13614043#comment-13614043
]
Karl Wright commented on CONNECTORS-664:
----------------------------------------
bq. 1 question regrading NTLM; does the repo connector treat the domain the
same way as the authority?
The connector and authority should be identical as far as the way the domain is
treated.
bq. Regarding NTLM; I just wanted to restate that yes some people use the
domain in the opentext username and some don't.
Explicitly setting the domain is what triggers NTLM. So here are the
combinations:
- server NTLM Domain set, server NTLM user name has no domain included: NTLM
enabled; domain will be as specified, full domain and user will be
<domain>\<user>
- server NTLM domain NOT set, server NTLM user name is set: basic auth used; no
NTLM; basic auth user name is exactly what the user entered
- server NTLM user name NOT set: No http auth used
I think that covers all the useful cases, no?
> Livelink connector: Add support for SSL LAPI communication
> ----------------------------------------------------------
>
> Key: CONNECTORS-664
> URL: https://issues.apache.org/jira/browse/CONNECTORS-664
> Project: ManifoldCF
> Issue Type: Improvement
> Components: LiveLink connector
> Affects Versions: ManifoldCF 1.1.1
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 1.2
>
>
> David Morana has requested that the livelink connector be modified to support
> Livelink's SSL communication protocols. This will involve a cert for this
> purpose, as well as be enabled by selection, so there are UI changes
> required. There is also another LAPI jar involved: llssl.jar
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
