Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
THRUST SERVICES & TOOLS
CLOUD EDITIONS
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Content Management (Extended ECM)
API, SDK, REST and Web Services
NTLM Authentication
Martin_Krenn
Hi !We have a strange problem on our Server with the NTLM Authentication.In the browser it works and with the Livelink Explorer not.See document in annex.Maybe or hopefully somebody is able to helpThanksMarco
Find more posts tagged with
Comments
Fabienne_GUIMET
Does it occur for every users ? on every postes ?You should try first to reinitialise the user profil.I had similar problems with LLExplorer 4.4.2 and LES 9.2 SP1 for a few users, this only solution was to delete their NT account and recreate it. The support did not find the reason and thought the problem was the windows SID...Hope this give you some ideas !Fabienne
Janusz_Frydecki
If you have access to LL Builder, you could try to break in WebDSP.RequestHandlerSubsystem.Dispatch() and from there, dive until you get to the authentication part and there you should find what the problem is.
Guy_Pomerleau
I suggest you enable logging then look at the connect.log file in your logs directory. Here are steps to enable the logging I am after: 1) open the opentext.ini file 2) set debug=2, wantLogs=TRUE, wantVerbose=TRUE, wantTimings=TRUE 3) save the opentext.ini file 4) restart the livelink services 5) reproduce the error We have LL 9.5Sp1 and LL explorer 4.7.0 and it is working fine
Chris_Wagg
Message from Chris Wagg via eLinkThere are a few things that could be happening here. You may need toreset passwords to hidden for your users. Livelink Explorer stillrequires that your password be hidden if you are using NTLMauthentication, and you will see this sort of error when trying toconnect through Explorer.Also, have you populated the CGIHosts field on the Choose DirectoryServices page? You need to have the loopback address and the IP addressof any Livelink servers that you have included here. It should looklike this:127.0.0.1,123.10.10.1If you have done these and are still having trouble, I would recommendopening a ticket with support. Be sure to include the Livelink logsthat Guy suggested.---------------------------------------Chris WaggSenior Product SpecialistOpen Text CorporationPh: 800-540-7292Email: cwagg@opentext.com--------------------------------------------Original Message-----From: eLink Discussion: Livelink Directory Services Discussion[mailto:directoryservices@elinkkc.opentext.com] Sent: Thursday, August 31, 2006 2:39 PMTo: eLink RecipientSubject: NTLM AuthenticationNTLM AuthenticationPosted by Pomerleau, Guy on 08/31/2006 02:34 PMI suggest you enable logging then look at the connect.log file in yourlogs directory. Here are steps to enable the logging I am after: 1) open the opentext.ini file 2) set debug=2, wantLogs=TRUE, wantVerbose=TRUE, wantTimings=TRUE 3) save the opentext.ini file 4) restart the livelink services 5) reproduce the error We have LL 9.5Sp1 and LL explorer 4.7.0 and it is working fine[To reply to this thread, use your normal E-mail reply function.]============================================================Topic: NTLM Authentication
https://knowledge.opentext.com/knowledge/llisapi.dll/open/7693050Discussion
: Livelink Directory Services Discussion
https://knowledge.opentext.com/knowledge/llisapi.dll/open/3062146Livelink
Server:
https://knowledge.opentext.com/knowledge/llisapi.dllTo
Unsubscribe from this Discussion, send an e-mail tounsubscribe.directoryservices@elinkkc.opentext.com.
Martin_Krenn
yes, it is for every user.
Martin_Krenn
yes i will try as soon as the indexveriÃcation is ready.
Janusz_Frydecki
What is the exact role of the CGIHosts field? On our installation, we alway set it only to the loopback, what is the impact?
eLink User
Message from Hetz, Michael \(GE, Research\) via eLinkLivelink will reject any cgi request (livelink server to server request)from a system not in that list. We have several livelink front ends, so all those IP addresses are inthat list.Basically, any livelink server should be in that list.In our example, here are the entries that we have in that list.1) All Livelink servers in our Livelink instance2) All remote cache servers globally3) The IP address of the load balancer virtual server that fronts ourlivelink instance.Mike HetzMichael C. HetzGE Global ResearchAdvanced Information Technologies