Highlighted
Absent Member.
Absent Member.
469 views

Problem to enable ssl on publisher channel of SOAP Driver


Hi,
currently we wanna establish a secure connection between our IDM and
web-application. For that i followed the steps scripted in the chapter
6.1 of
"http://www.novell.com/documentation/idm401drivers/pdfdoc/soapdriver/soapdriver.pdf"-guide.
Unfortunately its not working that easy. Cant start the driver anymore
and get this error in the trace. We set up the IDM-4.0.1-Advanced
Evaluation Linux system. Without ssl its working. Do we have to specify
something else in the remoteloader-config file for ssl?
So its seems that it cannot find the NTLSSocket-class. Where it should
be usually? Or did we miss anything. Hope somebody has an idea.

[11/10/2011 8:53:30.470] ASA Notification Feed PT:
DirXML Log Event -------------------
Driver: \IMS-INT\system\driverset1\ASA Notification Feed
Channel: Publisher
Status: Fatal
Message: Exception caused by PublicationShim.init()
java.lang.NoClassDefFoundError: Could not initialize class
com.novell.nds.ntls.NTLSSocket
at
com.novell.nds.ntls.NTLSServerSocket.<init>(NTLSServerSocket.java:70)
at
com.novell.nds.ntls.NTLSServerSocket.<init>(NTLSServerSocket.java:175)
at
com.novell.nds.dirxml.driver.ssl.ntls.NTLSKmoFactory.createServerSocket(NTLSKmoFactory.java:101)
at
com.novell.nds.dirxml.driver.soap.SSLFactoryListener.newServerSocket(SSLFactoryListener.java:57)
at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)
at
org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:283)
at
org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:147)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.Server.doStart(Server.java:235)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
com.novell.nds.dirxml.driver.soap.HTTPPublisherTransport.init(HTTPPublisherTransport.java:114)
at
com.novell.nds.dirxml.driver.soap.SOAPPublisher.init(SOAPPublisher.java:196)
at com.novell.nds.dirxml.remote.loader.Driver.run(Driver.java:809)
at java.lang.Thread.run(Unknown Source)
[11/10/2011 8:53:30.470] ASA Notification Feed PT:
DirXML Log Event -------------------
Driver: \IMS-INT\system\driverset1\ASA Notification Feed
Channel: Publisher
Status: Fatal
Message: Code(-9005) The driver returned a "fatal" status
indicating that the driver should be shut down. Detail from driver:
Exception caused by PublicationShim.init()
java.lang.NoClassDefFoundError: Could not initialize class
com.novell.nds.ntls.NTLSSocket
at
com.novell.nds.ntls.NTLSServerSocket.<init>(NTLSServerSocket.java:70)
at
com.novell.nds.ntls.NTLSServerSocket.<init>(NTLSServerSocket.java:175)
at
com.novell.nds.dirxml.driver.ssl.ntls.NTLSKmoFactory.createServerSocket(NTLSKmoFactory.java:101)
at
com.novell.nds.dirxml.driver.soap.SSLFactoryListener.newServerSocket(SSLFactoryListener.java:57)
at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)
at
org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:283)
at
org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:147)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at org.mortbay.jetty.Server.doStart(Server.java:235)
at
org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
at
com.novell.nds.dirxml.driver.soap.HTTPPublisherTransport.init(HTTPPublisherTransport.java:114)
at
com.novell.nds.dirxml.driver.soap.SOAPPublisher.init(SOAPPublisher.java:196)
at com.novell.nds.dirxml.remote.loader.Driver.run(Driver.java:809)
at java.lang.Thread.run(Unknown Source)
<application>DirXML</application>
<module>ASA Notification Feed</module>
<object-dn></object-dn>
<component>Publisher</component>
[11/10/2011 8:53:30.471] ASA Notification Feed PT:Killing driver from
publisher thread; after PublicationShim.start().
[11/10/2011 8:53:30.471] ASA Notification Feed PT:Requesting
termination.
[11/10/2011 8:53:30.471] ENG EV: SetDriverStateHandler: setting driver
<cn=ASA Notification Feed,cn=driverset1,o=system> state to <3>
[11/10/2011 8:53:30.472] ENG EV: SetDriverStateHandler: reporting state
change to <3> for driver <cn=ASA Notification
Feed,cn=driverset1,o=system>, initiated by
<cn=intdirectory01,ou=servers,o=system>
[11/10/2011 8:53:30.472] ASA Notification Feed PT:Ending publisher
thread.
[11/10/2011 8:53:31.396] ASA Notification Feed
ST:SubscriptionShim.execute() returned:
[11/10/2011 8:53:31.396] ASA Notification Feed ST:
<nds dtdversion="4.0" ndsversion="8.x">
<output>
<status event-id="query-driver-ident" level="retry"
type="remoteloader">No connection to remote loader</status>
</output>
</nds>


--
robinkir
------------------------------------------------------------------------
robinkir's Profile: http://forums.novell.com/member.php?userid=113051
View this thread: http://forums.novell.com/showthread.php?t=448037

Labels (1)
0 Likes
2 Replies
Highlighted
Absent Member.
Absent Member.

Re: Problem to enable ssl on publisher channel of SOAP Driver

robinkir,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: Problem to enable ssl on publisher channel of SOAP Driver

Are you:

1) trying to enable SSL between the engine and the Remote Loader?


2) Or for the SOAP Endpoint that is listening on the Remote Loader?

Both use SSL but totally differently.

In case 1, the cert that starts it resides in eDirectory, and the RL
needs a copy of the Trusted Root's Public key. (In a Winders RL you see
this as a file system reference to a B64 encoded file. With the Java
remote loader you can specify either a file (Oddly enough, DER/PEM
encoded, (binary not B64)) or a JKS keystore file (and password on the
file) for your instance of the RL.

In case 2, I am pretty sure that although the docs do not mention it,
the Keystore needs to be on the remote loader server, and referenced by
thr RL configuration. (They are basically discussing running the SOAP
driver local in the engine in the docs).



On 11/10/2011 3:16 AM, robinkir wrote:
>
> Hi,
> currently we wanna establish a secure connection between our IDM and
> web-application. For that i followed the steps scripted in the chapter
> 6.1 of
> "http://www.novell.com/documentation/idm401drivers/pdfdoc/soapdriver/soapdriver.pdf"-guide.
> Unfortunately its not working that easy. Cant start the driver anymore
> and get this error in the trace. We set up the IDM-4.0.1-Advanced
> Evaluation Linux system. Without ssl its working. Do we have to specify
> something else in the remoteloader-config file for ssl?
> So its seems that it cannot find the NTLSSocket-class. Where it should
> be usually? Or did we miss anything. Hope somebody has an idea.
>
> [11/10/2011 8:53:30.470] ASA Notification Feed PT:
> DirXML Log Event -------------------
> Driver: \IMS-INT\system\driverset1\ASA Notification Feed
> Channel: Publisher
> Status: Fatal
> Message: Exception caused by PublicationShim.init()
> java.lang.NoClassDefFoundError: Could not initialize class
> com.novell.nds.ntls.NTLSSocket
> at
> com.novell.nds.ntls.NTLSServerSocket.<init>(NTLSServerSocket.java:70)
> at
> com.novell.nds.ntls.NTLSServerSocket.<init>(NTLSServerSocket.java:175)
> at
> com.novell.nds.dirxml.driver.ssl.ntls.NTLSKmoFactory.createServerSocket(NTLSKmoFactory.java:101)
> at
> com.novell.nds.dirxml.driver.soap.SSLFactoryListener.newServerSocket(SSLFactoryListener.java:57)
> at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)
> at
> org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:283)
> at
> org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:147)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.Server.doStart(Server.java:235)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> com.novell.nds.dirxml.driver.soap.HTTPPublisherTransport.init(HTTPPublisherTransport.java:114)
> at
> com.novell.nds.dirxml.driver.soap.SOAPPublisher.init(SOAPPublisher.java:196)
> at com.novell.nds.dirxml.remote.loader.Driver.run(Driver.java:809)
> at java.lang.Thread.run(Unknown Source)
> [11/10/2011 8:53:30.470] ASA Notification Feed PT:
> DirXML Log Event -------------------
> Driver: \IMS-INT\system\driverset1\ASA Notification Feed
> Channel: Publisher
> Status: Fatal
> Message: Code(-9005) The driver returned a "fatal" status
> indicating that the driver should be shut down. Detail from driver:
> Exception caused by PublicationShim.init()
> java.lang.NoClassDefFoundError: Could not initialize class
> com.novell.nds.ntls.NTLSSocket
> at
> com.novell.nds.ntls.NTLSServerSocket.<init>(NTLSServerSocket.java:70)
> at
> com.novell.nds.ntls.NTLSServerSocket.<init>(NTLSServerSocket.java:175)
> at
> com.novell.nds.dirxml.driver.ssl.ntls.NTLSKmoFactory.createServerSocket(NTLSKmoFactory.java:101)
> at
> com.novell.nds.dirxml.driver.soap.SSLFactoryListener.newServerSocket(SSLFactoryListener.java:57)
> at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)
> at
> org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:283)
> at
> org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:147)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at org.mortbay.jetty.Server.doStart(Server.java:235)
> at
> org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
> at
> com.novell.nds.dirxml.driver.soap.HTTPPublisherTransport.init(HTTPPublisherTransport.java:114)
> at
> com.novell.nds.dirxml.driver.soap.SOAPPublisher.init(SOAPPublisher.java:196)
> at com.novell.nds.dirxml.remote.loader.Driver.run(Driver.java:809)
> at java.lang.Thread.run(Unknown Source)
> <application>DirXML</application>
> <module>ASA Notification Feed</module>
> <object-dn></object-dn>
> <component>Publisher</component>
> [11/10/2011 8:53:30.471] ASA Notification Feed PT:Killing driver from
> publisher thread; after PublicationShim.start().
> [11/10/2011 8:53:30.471] ASA Notification Feed PT:Requesting
> termination.
> [11/10/2011 8:53:30.471] ENG EV: SetDriverStateHandler: setting driver
> <cn=ASA Notification Feed,cn=driverset1,o=system> state to<3>
> [11/10/2011 8:53:30.472] ENG EV: SetDriverStateHandler: reporting state
> change to<3> for driver<cn=ASA Notification
> Feed,cn=driverset1,o=system>, initiated by
> <cn=intdirectory01,ou=servers,o=system>
> [11/10/2011 8:53:30.472] ASA Notification Feed PT:Ending publisher
> thread.
> [11/10/2011 8:53:31.396] ASA Notification Feed
> ST:SubscriptionShim.execute() returned:
> [11/10/2011 8:53:31.396] ASA Notification Feed ST:
> <nds dtdversion="4.0" ndsversion="8.x">
> <output>
> <status event-id="query-driver-ident" level="retry"
> type="remoteloader">No connection to remote loader</status>
> </output>
> </nds>
>
>


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.