IGEL UMS Certificate File Classification Explained

In the IGEL Community, a member asked the following question relating to IGEL UMS Certificates. We wanted to share it with all of you, as it's a goodie.

Question:

Can you explain what actually happens when you choose a different file classification when using UMS to upload a certificate to a device? I presume it just gets copied to a different location on the file system. The classifications I’m referring to are:

• Undefined

• Web Browser Certificate

• SSL Certificate

• Java Certificate

• IBM iAccess Certificate

• Common Certificate (All Purpose)

Answer:

It tells the OS where it should actually link the certificate to in the file system and which applications will get access to them.

There are two special types:

• Undefined - This is for non-ssl files being deployed to the endpoint. Maybe a custom script or some special binary required for your workflow. Usually deployed to /wfs for consistency, but be cautious as wfs does not have unlimited space

• Undefined - This is for non-ssl files being deployed to the endpoint. Maybe a custom script or some special binary required for your workflow. Usually deployed to /wfs for consistency, but be cautious as wfs does not have unlimited space

If you are unsure what the cert is for, it is safe to use Common Certificate (All Purpose).

This copies the file to /wfs/ca-certs/ and IGEL OS will link those certificates to the correct places in the OS at every boot

Learn more and/or leave a comment or question, read IGEL UMS Certificate File Classification Explained in the IGEL Community on Slack. Not a member? Join Now!