Hello Otto, hello all,
On 28/08/2021 04:37, Otto, Karsten Andreas wrote:
> On 27.08.21 16:42, Raphaël Ouazana-Sustowski wrote:
>> I'm in favor of getting rid of keystore in favor of PEM format (or at
>> least allowing both).
>>
> If at all possible please allow both; in our setup we use the same
Benoit Tellier created JAMES-3638:
-
Summary: Allow alternative keystore formats like PKCS12
Key: JAMES-3638
URL: https://issues.apache.org/jira/browse/JAMES-3638
Project: James Server
Issue
On 27.08.21 16:42, Raphaël Ouazana-Sustowski wrote:
>
> I'm in favor of getting rid of keystore in favor of PEM format (or at
> least allowing both).
>
If at all possible please allow both; in our setup we use the same
keystore for multiple service endpoints in addition to the mail server.
Hello,
Le 27/08/2021 à 06:37, Duc Nguyen a écrit :
Conclusion:
With Kubernetes and containers have become virtually synonymous with
cloud-native development, Apache James needs to adapt quickly and catch up
with others.
JKS keystore is an old topic but I'm bringing this back because the
Hello Duc,
I agree that JKS format is a pain to create and is a barrier to adoption.
Note to mention that JKS use is deprecated and that JKS is considered a
propretary format.
But rather than replacing it, I wonder if the approach of handling both
the JKS format and the key+cert format would
BUILD-FAILURE: Job 'james/ApacheJames/master [master] [247]':
Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames/job/master/247/;>james/ApacheJames/master
[master] [247]"
-
To unsubscribe, e-mail:
