Utilize Authentication Manager SDK 8.0 in non-weblogic environment
Originally Published: 2013-07-12
Article Number
Applies To
Java
Issue
Using default Weblogic EJB connection in non-Weblogic environment (Tomcat for example) does not deploy successfully
com.sun.xml.ws.api.wsdl.writer.WSDLGeneratorExtension: Provider
weblogic.wsee.jaxws.framework.policy.WSDLGeneratorExtension is
specified in jar:file:<appserver path>/lib/wlfullclient.jar!/META-INF/services/com.sun.xml .ws.api.wsdl.writer.WSDLGeneratorExtension
but not found
Cause
Resolution
1) Define application classpath to include the SDK jar files described by parameter classpath.run.httpinvoker in SDK_HOME/samples/common-build.xml
2) Define javax.net.ssl.trustStore to point to keystore that the Authentication Manager's root certificate was imported into.
3) Ensure that config.properties parameter ims.httpinvoker.client.provider.url is created and set equal to https://<AM FQDN>:7002/ims-ws/httpinvoker/CommandServer
4) Modify the following line of connection code to specify the HttpInvoker:
//Connection conn = ConnectionFactory.getConnection();
Connection conn = ConnectionFactory.getConnection("HttpInvokerCommandTargetBasicAuth");
OR
Rather than modify the connection code instead define the parameter: ims.client.primary.command.target = HttpInvokerCommandTargetBasicAuth
Notes
Related Articles
How to use the VBScript sample script of RSA Authentication Manager 8.x SDK 82Number of Views RSA Authentication Manager SDK 8.5 (for Java) failed on startup with a "CRED_MISMATCH" error 293Number of Views Error "Key negotiation exchange failed. Server response was CRED_MISMATCH" with RSA Authentication Agent SDK 8.6 for Java 237Number of Views Authentication Takes Too Long When Using RSA Authentication Agent SDK 8.1.3 for Java on Red Hat 90Number of Views RSA Identity Governance and Lifecycle IBM Lotus Notes (Domino) collector does not collect group data. 50Number of Views
Don't see what you're looking for?