nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OTDS 10.5 and CS 10.0. - SOAP Exception thrown in validation of user

Anthony Miller

Hi,

Content Server 10 Update 2014-12 (version 10.0.0.3187)

OTDS Version: 10.5.0 SP1 with Patch 5 (10.5.0.1282 2014-12-11 20:45:56).

Using the CWS, I am getting a SOAP Exception thrown when trying to validate the user. I can authenticate (and get the token returned from OTDS for the username and password passed in), however when the call is made to validte the user, a SOAP exception is thrown.

I'm wondering if there is a incompatibility between the versions I have. I am referencing les-services from IIS and otdsws from tomcat.

The source code below is from the CWS Content Server 10.5 documentation.

Be grateful if someone has any experience of getting this configuration to work for CWS (I have it working for Portal 8.5 and CS 10 without a problem).

Thanks in advance,

Anthony

OTDS.java.txt

Find more posts tagged with

Comments

Appu_Nair1

Essentially in these cases the protocol is like this.On the livelink server where you are sending the work,after obtaining the token needs to accept the userid.Typical problems are the same named(CaSe,Domain included) userid should exist in livelink.For e.g if your userid is OTDS is appunair then a same named user should exist in livelink when you search for users and groups in livelink not OTDS. Other avenues are you can increase logging on the livelink server by putting debug=2,wantlapilogs=true,wantlogs=true those will indicate why livelink is rejecting the token(encrypted userd passed to livelink).Also simple GUI tests as the OTDS user should validate why this is happening since whatver the API is doing 9 out of 10 times you should be able to perfom the same as the same user.

Anthony Miller

Hi Appu,

Yep, this is pretty weird actually. I've got logs on in full and am working my way through them to see if there is anything that points me in the right direction.

Part of me is thinking that there is some underlying issue with the web service endpoints that I create via the wsimport commands (albeit that these are the ones in the CWS documentation!). Also, as the OTDS.java code is for 10.5 and I have CS 10 in my environment but have OTDS 10.5, whether there is some incompatibility that is currently unknown.

We are not due to upgrade our production environment to 10.5 until much later in the year but the solution we are developing soon needs to be targetted at our current 10.0 environment.

It has been suggested to create a hybrid solution using REST and CWS whcih may work (I haven't tested this yet though).

What I would ideally like to find is a demo piece of code which uses but which was targetted at CS10 and not 10.5 just to see if there is a difference somewhere or actually whether I have found a bug.

Thanks,

Anthony

Appu_Nair1

Hi Anthony,

I think your immediate problem is that you have OTDS10.5 and CS10 combination and you want the OT published source code to work so the better avenue is through a ticket. However using simple tools like Fiddler and livelink debugging if one were interested one could find out if communication was occurring and if livelink is returning the SOAP Exception. However I am adventurous when it comes to OT software so likes to tinker more.

Since OTDS is nothing but a simple authentication provider I would amend that OT code to use OTDS and using your knowledge I will go to the server hosting the WSAPI end points and find out what WSDL's are on tap and see if it is configured to talk to a valid livelink server. For e.g. in the WCF implementation the les-services is for CS10 and in CS10.5 it is called cws. So my wsimport will be the valid WSDL's for that 10 livelink server. If 10 code is not published for I would use 971 code. In any case I would put the WSDL's in a browser to see if they are correct (note WSDL checking in a browser is just to know the methods NO communication to livelink through Web.Config is happening when you do that)

So wsimport for OTDS if like the CS10.5 And wsimport for livelink using the older wsdl code.

I have used the brand new 10.5 end point to talk to 10.5,10 and 9.7.1 and I am not concerned with OTDS since we are a pure DMS solution so does not require the authentication of OTDS as core livelink has an authentication web service. I have also code that piggy backs on IWA (SSO) as our servers use IWA (SSO) by windows. Using the latest web services code against an old livelink will have its consequences but I don't think OT prevents it .What you will most likely end is if the call is implemented only in the WSDL but the actual livelink server does not support it won't work that is all. I try in my mind or a piece of paper to understand the role of each player(service) and it helps me tremendously using simple methods of debugging like I provided earlier because if livelink is supposed to do something as a user, if that user is not allowed in livelink that will not happen. Whether API, GUI or rest...

Pls share your results if OT determines if this is a bug...