1

I am trying to install a cert from our root CA to our (internal only) spiceworks install. I however have not found a way to do this.

I have tried the following:

https://community.spiceworks.com/how_to/128845-the-secure-way-to-secure-spiceworks

https://community.spiceworks.com/how_to/127889-creating-and-incorporating-a-public-ssl-certificate-for-spiceworks

A problem (?) I run into is the CA is a Windows server. As far as I can tell, it does not give me the option to download the certs in a .PEM format which is what I am replacing in the Spiceworks server.

Has anyone used a Windows server root CA to assign a cert to a spiceworks install?

4 Spice ups
2

IF you generate the certificate via the webserver login https://yourCA/certsvr then you should be able to save in one of two formats.

You can convert using OpenSSL or go here

Personally I don’t bother using SSL on the internal side

1 Spice up
3

Thanks, I will give this a try. Our examiner this year (and next) will make it a finding if we allow AD credentials to be sent to a http site…so its a requirement for us.

4

Does this apply to all of your intranet sites, my guess is this does not.

I would hazard a guess they know it can handle HTTPS due to seeing a self-signed certificate and they’ve asked you to correct that.

It’s never once come up on our PCI tests and we have to have some very rigorous tests

5

We are not (yet) held to PCI standards, just NCUA. But the auditor did say unofficially we need to work on getting certs on any internal site that requires credentials. He wants to see an effort was made before our next audit in July 2017.

Not to mention my manager has said “make it so” because he is afraid of how users will react when they see the warnings (current ticketing platform is all http, so no warnings).

6

I think that seems a little harsh, most intranets don’t use SSL by default, while they can there I no confidential data there, likewise these are just tickets.

Try the above though and if you need further help let me know.

1 Spice up
7

It does not bother me. Gives me something new to learn/do. Thanks again!

8

Thanks for your help, this is working now!

9

If you found any of my posts helpful please mark them as so and if you’ve solved this please mark a best answer, even if your own so others can quickly find the solution

1 Spice up
10

Also for others: I followed the second link above but did not use the FQDN in the CSR since the URL the website is running is not using the FQDN.

Firefox and Chrome don’t like that its using SHA1, but IE throws no errors so that is all I needed to complete this task.