Re: DCM - not able to apply certificate to application

excellent! I imported the certificate from work with server and client
certificates.

What had happened was initially I got a message saying:
An error occurred during certificate validation. The issuer of the
certificate may not be in the certificate store or the issuer may not be
enabled.

Comodo then sent me 3 CA certificates. I imported them using "work with CA
certificates". And I also imported the server certificate from that
option.

The naming of these things is kind of confusing. I was thinking a CA
certificate was an SSL certificate that has been issued by a trusted source.



On Mon, Oct 8, 2018 at 8:10 AM Bradley Stone <bvstone@xxxxxxxxx> wrote:

You didn't import the actual certificate, then. It looks like you imported
the CA, but the not actual certificate.

The info you get from them should include:

1. The CAs
2. The Actual Certificate.

The certificate is imported using Work with Server and Client Certificates,
then Import, from DCM.

Bradley V. Stone
www.bvstools.com


On Sun, Oct 7, 2018 at 9:23 AM Steve Richter <stephenrichter@xxxxxxxxx>
wrote:

does not show up in "work with server and client certificates.
but they are listed under "work with CA certificates".

*Work with CA Certificates*

*Certificate type: *Certificate Authority (CA)
*Certificate store: **SYSTEM

Select a certificate, then select a button to perform an action on the
certificate.

If you want to include a CA in the CA trust list for an application,

select

a CA from the list below and click the Enable button. A list of
applications will display and you can select the applications that should
include this CA in the application's CA trust list.

*Certificate Authority (CA)**Status*

follow54_com Enabled
COMODORSADomainValidationSecureServerCA Enabled
COMODORSAAddTrustCA Enabled
AddTrustExternalCARoot Enabled
LOCAL_CERTIFICATE_AUTHORITY_067454R1(1) Enabled


On Sun, Oct 7, 2018 at 8:34 AM Bradley Stone <bvstone@xxxxxxxxx> wrote:

Did you import it as a server certificate? Does it show up in Work

with

Server and Client certificates? If so, select it, and click "Assign to
Applications" and assign it that way.

You shouldn't need to define a CA trust list for the application.

Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #12 <https://www.bvstools.com/mailtool.html>: Both

Text

and HTML email support

On Sat, Oct 6, 2018 at 8:03 PM Steve Richter <stephenrichter@xxxxxxxxx

wrote:

I have imported a signed digital certificate from Comodo ( via

namecheap

)

problem is, when I "update certificate assignment" of the

application,

the

signed certificate is not shown in the list of available

certificates.

How

to get my certificate in that list?

Was able to define a "ca trust list" for the application. The signed
certificate was listed there.

*Application type: *Server
*Application ID: *QIBM_HTTP_SERVER_ZENDPHP7
*Application description: **(No description)*

Only define a CA Trust List if the list will be a subset of the

eligible

CAs. See the online help for more information.

The Certificate Authorities (CAs) defined in the CA trust list for

the

application are checked. If you wish to change the trust list, click

on

the check box and select OK.

*Certificate Authority (CA)*
follow54_com
COMODORSADomainValidationSecureServerCA
COMODORSAAddTrustCA
AddTrustExternalCARoot
LOCAL_CERTIFICATE_AUTHORITY_067454R1(1)
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our

affiliate

link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD