indranil2121 Absent Member.
Absent Member.
237 views

Scripting driver certificate issue

We have a support project where have a scripting driver connecting to a windows system. In driver remote loader option, there is the path of remote loader server and a KMO ssl certificate used. But in seeing remote loader server there are no remote loader installed in it. A service(NetIQ scripting service) is running in the system. In Novell\WSDriver folder there is a config folder. In config folder a certificate path is given. It's Novell\WSDriver\Keys\cert.pem.
Now we don't have any clue is this the only certificate used. Also we don't have any idea what is the certificate for ( Is that a root CA organization tree cerificate or SSL DNS certificate).

It would be great if I get some idea.
Labels (1)
0 Likes
1 Reply
Knowledge Partner
Knowledge Partner

Re: Scripting driver certificate issue

On 4/15/2019 5:14 AM, indranil2121 wrote:
>
> We have a support project where have a scripting driver connecting to a
> windows system. In driver remote loader option, there is the path of
> remote loader server and a KMO ssl certificate used. But in seeing
> remote loader server there are no remote loader installed in it. A
> service(NetIQ scripting service) is running in the system. In
> Novell\WSDriver folder there is a config folder. In config folder a
> certificate path is given. It's Novell\WSDriver\Keys\cert.pem.
> Now we don't have any clue is this the only certificate used. Also we
> don't have any idea what is the certificate for ( Is that a root CA
> organization tree cerificate or SSL DNS certificate).


I was looking at some of my old articles and one with one of the highest
page views was this one:
https://www.novell.com/communities/coolsolutions/many-faces-remote-loaders-idm/

The second type in there is the one Scripting uses. So it is the IDM
Scripting service, yes, not a standard remote loader. The certificate
you have, you know you can decode that, right?

Drop the text into this web site:
https://www.sslshopper.com/certificate-decoder.html

I can pretty much guarentee however it is the public key of the CA that
signed the SSL CertificateDNS private key.

Then scheck out the docs for the Scripting driver here:
https://www.netiq.com/documentation/identity-manager-47-drivers/bi_impl_scripting/data/bi_impl_scripting.html#b8mow8v




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.