To give you a better view, here's the message. > Files are in /home/centos/tls/company.com-wildcard. Are we using Gluu with Tomcat? If so, I think you should follow the instructions in getting_started-java.txt and simply use the company.p7b file. Please keep all of these files secret, especially company.key, company.crt, and company.p7b. The best policy is to limit permissions to just what is needed (which I've done for the files in this folder) -- including any copies you make on the server for configuration -- and also never transfer these files anywhere off the server (which you shouldn't need to anyway).

You need a x509 certificate and private key ( both no-password-protected ) for your Gluu Server's apache cert update.

Remember that SAML uses self-signed certificates--chains are not supported by either the Shibboleth IDP or Asimba. You can do whatever you like with the Apache config in the chroot container. We give you the Apache config as a starting point, but many customers have their own conventions for the management of Apache httpd.

Why does it ask me for passwords when importing .p7b file, I asked our director and he said he didn't put any passwords in it. I just used this command inside chroot. ``` keytool -importcert -alias <hostname_of_your_Gluu_Server>_httpd -trustcacerts -file [company_name].p7b -keystore cacerts -alias <hostname_of_your_Gluu_Server>_httpd ```

Would you guys be able to help me on how to import this certificate just to remove the unsecure connection notification from our browsers. I have the ff files: company.key, company.crt, and company.p7b

Hi, Karl. Please note that using 2.4.4 packages is discouraged as the most recent one is 3.0.1. You should only use it if it's a previously installed live instance. Have you checked our certificate updating guide for 2.4.x [here](https://gluu.org/docs/ce/2.4.4/admin-guide/certificates/)? It provides all needed steps to achieve what you need (which is, I suppose, update of Apache's certificate, is it correct?) Your command doesn't seem correct to me. You should try something like this instead: 1. Backup your instance 2. Remove previous certificate: `# keytool -delete -alias <hostname_of_your_Gluu_Server>_httpd -keystore /usr/java/latest/lib/security/cacerts -storepass changeit` 3. Install new one: `# keytool -importcert -alias <hostname_of_your_Gluu_Server>_httpd -trustcacerts -file company.crt -keystore /usr/java/latest/lib/security/cacerts -storepass changeit` 4. Restart Tomcat Please also note that you may need to also update certificate Apache itself uses, and also point it to a file containing intermidiate certificates for your new certificate. Those are standard Apache admin procedures and mentioned in the guide I referenced above.

Karl, please also check [this page](https://gluu.org/docs/ce/2.4.4/operation/update-certificate/), it provides more detailed explanations.