Currently trying to configure WebLogic web service to connect with non-WebLogic client for message-level encryption. It was suggested the following resources might hold the key. So far, my problem doesn't seem to involve any of these, rather a problem with certificates that have been set up properly with certificate chaining.
Oracle Fusion Middleware Documentation: Attaching Policies - 12c (12.1.2)
http://docs.oracle.com/middleware/1212/owsm/OWSMS/attach-owsm-policy.htm#OWSMS5613- http://docs.oracle.com/middleware/1212/owsm/OWSMS/attach-owsm-policy.htm#OWSMS5613
- http://docs.oracle.com/middleware/1212/wls/WSSOV/owsm-security.htm#CHDBAHBI
It appears there are some proprietary resources that may be used to set up webservices using WebLogic. There are both Java code solutions as well as Java annotations to save the time of writing straight Java code.
weblogic.wsee.jws.jaxws.owsm.SecurityPolicyFeature class (single policy) weblogic.wsee.jws.jaxws.owsm.SecurityPoliciesFeature class (multiple policies)
Java / Oracle SOA blog: Calling an OWSM protected service with Axis 1.4 and WSS4J
http://biemond.blogspot.com.au/2011/09/calling-owsm-protected-service-with.html- http://biemond.blogspot.com.au/2011/09/calling-owsm-protected-service-with.html
- http://docs.oracle.com/cd/E21764_01/web.1111/e16098/interop_axis.htm#CHDCICGG
We're using Apache CXF. If you are using Fusion Middleware, there are some limitations to what Axis and WSS4J standards are supported.
...you can't use every OWSM policy with Axis. Oracle made an interoperability documentation page what is possible with Axis 1.4 and OWSM 11g, please check this first.
http://biemond.blogspot.com.au/2011/09/calling-owsm-protected-service-with.html
Oracle documentation provides some help on how you would create your webservices under various scenarios including SAML authentication/authorization and username token. Again, not useful in our case.
No comments:
Post a Comment