• 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
  • Tim Cooke
  • paul wheaton
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Interoperability .NET WSE2.0 MessageSignature

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

I am building a WS-client in JAVA for a .Net WS.

I have got an example for a .Net client:



I tried to build a JAVA-client with Apache Axis and Oracle JDeveloper and secured it with a Username Password. Appereantly this is unsufficient. When invoking the client the result is:



I thought the solution was in signing the message but the webservice-supplier told me that I did not need a key store or something like that.

Do you have any suggestions?


Regards,


Romano
 
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The code looks like you use both username/password and a signature. Is that what you want to do? In other words, is "context.Security.Elements.Add(new MessageSignature(userToken))" necessary?
 
Romano Londt
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Ulf Dittmer:
The code looks like you use both username/password and a signature. Is that what you want to do? In other words, is "context.Security.Elements.Add(new MessageSignature(userToken))" necessary?



Hi Ulf,

Thanks for the response.

I am only building the WS-proxy. The example is taken from a "manual" of the service provider. Therefore I do not have any influence on the serverside.

Regards,

Romano
 
Ulf Dittmer
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
In that case I would start with the WSDL description of the service. It'll tell you what the service expects, and you can use it to let your WS stack tools create Java stubs for accessing it.

Also, make sure the WS doesn't do anything that prevents non-DotNet clients from accessing it.
 
Romano Londt
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Ulf Dittmer:
In that case I would start with the WSDL description of the service. It'll tell you what the service expects, and you can use it to let your WS stack tools create Java stubs for accessing it.

Also, make sure the WS doesn't do anything that prevents non-DotNet clients from accessing it.



Ok,

I will mail you the wsdl.

I am not sure about yout last statement. I my knowledge doesn't reach that far.

regards,

Romano
 
Ulf Dittmer
Rancher
Posts: 43081
77
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I will mail you the wsdl.


Please don't: UseTheForumNotEmail
 
Romano Londt
Greenhorn
Posts: 14
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Ulf Dittmer:

Please don't: UseTheForumNotEmail



My Bad.

The wsdl :


 
knowledge is the difference between drudgery and strategic action -- tiny ad
Clean our rivers and oceans from home
https://www.kickstarter.com/projects/paulwheaton/willow-feeders
reply
    Bookmark Topic Watch Topic
  • New Topic