Consume .Net Webservices (SSO) via Java Client

Hi All,

Had anyone tried consuming .Net webservices( configured for Single Sign on) via Java client.

Environment: CS10, .Net WebSvc (Windows Authentication enabled) and security mode =TransportCredentialOnly and clientCredentialType="Windows" in webconfig, Java client

I was able to get data but it takes about 30secs to get the data where as when I use regular .net webservices using username & pwd to authenticate, it takes just 2secs to get node data.

It's fast when the .net webservices(SSO) consumed via .net client. The issue is only when using Java Client.

Any insights would be highly appreciated.

Mahesh

Find more posts tagged with

Comments

Appu_Nair1

Hi Mahesh,

Is your java program(the client) seeking a auth end point using the cws/les-services deployment(WCF on IIS) so is it like

http://localhost/<les-services>}<cws>/Authentication.svc or are you saying the authentication services is on tomcat like

http://localhost:8080/les-services/services/Authentication for a TC implementation to cash in on the REMOTE_USER some additional libraries like WAFFLE is needed correct.Only IIS with IWA gives you the REMOTE_USER very easily in my experience.

Perhaps if you put Fiddler or wire Shark you will be able to see where the things are slowing down.

I have just started on the path of OTDS authentication and I beleive in regular livelink operation it does a web re-direct to the TC server hosting the OTDS servlet with some indication of who you are.I don't know enough to say how they do it but in my experiments with OTDS I put IWA on and anonymous on the livelink website and in both cases it knows who I am,meaning it is smart enough to hit the OTDS servlet with your domain info.

Apart from the small minscule re-directs that happen between livelink,TC & OTDS,and OTDS to the DC if you put the OTDS authentication service I think you may have a one stop shop for auth.Sorry never tried it myself trying to understand OTDS now.

Doesnot help you but might give you some options to check here and there

Mahesh Pinnamaneni

Appu,

My CS WS was hosted on IIS and changed the les-services/web.config to use Windows authentication as shown below for each non-SSL bindings:

</security>

It takes most of the time when we instantiate DocumentManagement_Service object but the rest of the calls are pretty fast.

I should probably try wireshark to see where its slowing down. But the interesting thing is its fast with .Net client.

Thanks,

Mahesh

eLink User

That to me does not make a lot of sense.In fact it is very easy to see if it is client slowdown or livelink slowdown.You just have to put debug=2,
wantlapillogs=true
,wantsummarytimings=true
on your livelink server and re-attempt and capture timings

Then you start comparing the timings in your .NET attempt and Java attempt.Each WSAPI call like your DocumentManagement Service will be recorded in your thread logs as _inArgs and _outArgs with indication of time.You would also see this in the ThreadTimings.logs as well.

Or you may want to do a simple operation with SOAPUI which I guess was written in java...

..Appu

Never argue with idiots. They drag you down to their level, and then beat you with experience.
Eat one live toad the first thing in the morning and nothing worse will happen to you the rest of the day

via : Laugh IT Out: Dilbert’s Best Quotes

On Wed, Jun 11, 2014 at 8:52 AM, eLink Entry: Content Web Services Forum <otdncontentwebservices971forum@elinkkc.opentext.com> wrote:

Consume .Net Webservices (SSO) via Java Client Posted bymahesh.pinnamaneni@nih.gov (Pinnamaneni, Mahesh)On 06/11/2014 09:52 AM

Appu, My CS WS was hosted on IIS and changed the les-services/web.config to use Windows authentication as shown below for each non-SSL bindings: <security mode="TransportCredentialOnly">
<transport clientCredentialType="Windows" />
</security>

It takes most of the time when we instantiate DocumentManagement_Service object but the rest of the calls are pretty fast.

I should probably try wireshark to see where its slowing down. But the interesting thing is its fast with .Net client.

Thanks,
Mahesh

[To post a comment, use the normal reply function]
Topic: Consume .Net Webservices (SSO) via Java Client
Forum: Content Web Services Forum
Content Server: Knowledge Center