IOP Workshop 2018: GDS Client issues

[mregen]

The following bugs or unsupported use cases were found on the IOP workshop by GDS users:

• Try to create a new certificate just with a .der file / no private key. (Use case should not be supported, require public/private key pair or force to create new public/private key pair)
• Same as above, but try to create public/private key pair and private key is a .pem file. .pem is not saved. (Do not support use case)
• server registration: allow to read info from real server, even when in server pull
• %CommonApplicationData% is sometimes not replaced in public/private key field when saving certs. (Prevent use case?)
• Private key password support for all use cases. (new public/private keypair, signing)
• Create/sign cert when only a .pfx is available and required. (workaround: export .der, then sign etc.)
• Create a new .pfx from information in .der (clone cert, create new private/public keypair)
• Client Pull: Sometimes hostname of GDS server is added to cert list of domains
• Saving domain names in database doesn't seem to work?

[mregen]

Target timeframe to fix this is for the next workshop in fall'18