• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
Bartenders:
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

JAVA JAX-WS NTLM / Kerberos

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hello,

Has anyone confronted a situation where you had to introduce a JAX-WS consumer that is challenged to authenticate with NTLM to a .NET endpoint ? I can't seem to figure this out and some forum threads I read ended with "we gave up and crafted a .NET client", although these threads date back to 2011... I am able to send a request through SOAP-UI using NTLM / Kerberos authentication turned on but can't seem to figure out how to force client to do authentication on its own in java (version 6).

This a simple snippet


This has no effect and I don't know at this point if security manager supposed to be null when setting default authentication. I also really want to avoid this authentication to be global since from a bunch of WS clients communicating with different endpoints only one has to be this smart.

Do any of you have suggestions ?

P.S. In the end solution will be based on Apache CXF.

Thank you.
 
Consider Paul's rocket mass heater.
reply
    Bookmark Topic Watch Topic
  • New Topic