Why do I get "Invalid User/Password" when using LAPI remotely?

Hello,

On our test Livelink server 10 we have port 2099 open. When I connect to it with LAPI remotely, getStatusMessage() returns "Invalid username/password specified.". The status code is -2147482645. This happens at lapi_documents.AccessEnterpriseWS().

If I upload the same c# code to run on the server locally, it works with no modification.

Any idea why?

Find more posts tagged with

Comments

Appu_Nair1

What do you have on the opentext.ini file under security settings.

func=admin.securityvars and look for

Livelink Client Hosts:

Usually one has at least the local loopback there.I always prefer to put the IP addresses of livelink computers connected to the same database as well.Worth a check..It does not mean that you have to openit up for every client lapi computer but the intent is basically it will trust that coming from the server.

haoest

Hi Appu, thanks for the insight. This is all that is under [security] in opentext.ini

There is no func=admin.securityvar as you mentioned, nor Livelink client host.

Can you tell me the syntax for white-listing lapi client please?

Authentication=NTLM
directoryList=\support\,\filters\
CGIHosts=
CAP_WebService_Url=
checkNextURL=false
cgiDirectory=cgi
allowedNextURLSites={}
allowedNextURLPrefixes={}
disableLoginEnabled=1
disableLoginAttempts=5
disableLoginEmailAdmin=1
signinPageCookieExpirationMode=1
signinPageCookieExpireDays=8
openCmd=true
DirectoryService=NTLM
UsernameStyle=0
DomainAndName=FALSE
UsernameOption=lowercase
Authentication_User=REMOTE_USER
cookieExpirationTime=30
requestTokenTimeoutEnabled=1
requestTokenTimeout=300
cookieExpirationMode=1
httponlyCookies=false
cookieUserPWD=false
cookieOwnerID=false
cookiePWDExpireDate=false
cookieClientIPAddress=0
disableAutoPassword=true
hideContainerSize=false
filterString=
separatorString=
validHttpReferers={'http'}
viewAsWebPageCmd=true
trustedCrossDomains={''}

Appu_Nair1

Perhaps for CS10 you may have to enable it somwhere I remember reading about it somewhere.OT experts could help more than I do.I do not have a CS10 install to check

in 9.7.1 and all this how you would put a cgihost

[Security]
directoryList=\support\,\filters\
CGIHosts=127.0.0.1;and more ip4 addresses of livelink servers each separated by a ;

with CS10 and ipv6 you may end up doing something more and many times what you put there for lapi may break other things like websvcs.

Carsten_Kulms

The CGIHosts setting does not apply to LAPI connections.

First I would check the log files on the server. Maybe you have to increase the log level and/or enable LAPI logs (Set wantLAPILogs=TRUE in the [options] section of the server's /config/opentext.ini file)

haoest

I am not livelink admin, if you would be so kind, can you let me know how to increase the logging level, and also what should I look for in the log file?

Carsten_Kulms

You can set the logging level via the Administration at the Configure Server Parameters page; seehttps://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-h-agd/en/html/jsframe.htm?lleswba-h-agd-wba-confserver-params-bgI recommend "Detailed Thread Logging".The other setting can set in the opentext.ini configuration file only; seehttps://knowledge.opentext.com/knowledge/piroot/llescor/v100000/llescor-h-agd/en/html/jsframe.htm?lleswba-h-agd-wba-confserver-params-bgHowever, you have to be an administrator to do so.What to look for? I cannot provide a specific advise - look for whatever gets logged during processing of the failing request, if something looks strange, and/or different when issuing the request from the local machine versus when calling from a remote machine.

haoest

This matter is resolved. Our network configuration was not properly set for lapi to work.

I want to thank everyone for helping to pin point the problem.