Is there a reason or by design that I need to have root.pem / intermediate.pem and client.pem and a key when I add an ICG?
Are you going to implement DER encoded too? Or pfx with cert and key included?
Hi Johan. So we need the whole chain of the certs. That is normally the Root CA of the issuer (e.g. GoDaddy), then an intermediate cert, then yours (customer.ch customer.ch) and a private key. That’s by design.
A PFX is the Windows format of Certificates, in Linux we’re working with BASE64 format and files with cer/crt and pem extensions.
You need to convert the PFX file using “openssl for windows”.
Continue reading and comment on the thread ‘Is there a reason or by design that I need to have root.pem / intermediate.pem and client.pem and a key when I add an ICG?’. Not a member? Join Here!
Learn more, search the IGEL Knowledge Base
Ask a question or comment on the above message thread?Join or log in to the IGEL Community to ask us anything and meet other IGEL customers, partners, and EUC enthusiasts.
Submit a question, or Join Today!
Popular Message Threads
- How to change the default IGEL UMS admin password?
- How to Install IGEL OS via a Bootable USB Drive
- Receiving error: “Citrix Receiver cannot create a secure connection in this browser” when launching a secure connection from Firefox on IGEL OS
- Error “AM_ERROR_AUTH_NETWORK_ERROR ” adding store in Citrix Workspace App version 20.x on IGEL OS 11.04
- Where to delete the certificates that cause ‘invalid certificate’ when trying to import an IGEL into UMS?
- IGEL UMS Universal Update Error: “could not resolve host name”
- Citrix connection via Netscaler Error: “AM_ERROR_AUTH_NETWORK_ERROR” on IGEL OS