[ 
https://issues.apache.org/jira/browse/AIRAVATA-3397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258362#comment-17258362
 ] 

Marcus Christie commented on AIRAVATA-3397:
-------------------------------------------

As a workaround, in our prod environment, I had updated the keycloak Apache 
virtual host config to use the previous Letsencrypt certificate (certbot renews 
when there is about 1 month left, so the previous one was still good for 
another month or so.

I've tested in our dev environment and leaving out the client trust store works 
with the Letsencrypt certificates.

Once we move this change into the prod environment, I'll revert my changes to 
the Apache virtual host config file so that it is once again using the latest 
Letsencrypt certificate.

> Letsencrypt signing certificate changed
> ---------------------------------------
>
>                 Key: AIRAVATA-3397
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-3397
>             Project: Airavata
>          Issue Type: Bug
>          Components: Security
>            Reporter: Marcus Christie
>            Assignee: Marcus Christie
>            Priority: Major
>
> The Letsencrypt signing certificate we had imported into 
> client_truststore.jks is no longer working since the signing certificate 
> Letsencrypt uses has changed:
> - https://letsencrypt.org/2020/09/17/new-root-and-intermediates.html



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to