Re: HPT8351 after using DCM to update SSL Key for website

[Brad Stone <bvstone@xxxxxxxxx>]

1st step is to always run a report for expired certificates (client and
server and self-signed) and CAs.
2nd step is to delete anything expired.

then you most likely will need to import new CAs and then your certificate.

DCM is so weird when it comes to expired certs and CAs.  Even if they don't
apply to the specific cert they will just shut things down.

On Mon, Apr 14, 2025 at 12:41 PM Jim Franz <franz9000@xxxxxxxxx> wrote:

> I updated the SSL key for website (created the csr from existing) several
> weeks ago, trying to follow the 2024 V7r5 documentation i created, but
> noticed that DCM appears has changed/improved... uploaded key, added to
> application , validated - looked ok.
> Everything ran and tested fine and went live, ran fine for couple weeks,
> but over weekend the first restart of HTTP after the 2024 key would have
> expired, web instance failed for HPT8351 Secure Sockets session failed to
> initialize successfully.
> Under the application, the Trusted Certificate Authority entries were no
> longer in the config.
> I don't remember previous years having to re-establish for renewed keys
> (although my memory is waning).
> Was this something new within V7R5 or did i miss something?
> Jim Franz
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.