And keystore is not mandatory for these, you can also use PEM/KEY files
<!-- Alternatively TLS keys can be supplied via PEM files -->
<!-- <privateKey>file://conf/private.key</privateKey> -->
<!--
<certificates>file://conf/certs.self-signed.csr</certificates> -->
<!-- An optional secret might be specified for the private key
-->
<!-- <secret>james72laBalle</secret> -->
On Wed, May 21, 2025 at 3:37 PM Benoit TELLIER <btell...@linagora.com>
wrote:
> Hello Matt,
>
> The password is defined in the configuration of the TCP protocols that
> needs to access the keystore and can thus be changed to the one you did set.
>
> CF
> https://github.com/apache/james-project/blob/c80ea107886e8798f44c7e348e10f66371206b58/server/apps/jpa-app/sample-configuration/imapserver.xml#L36
>
>
> --
>
> Best regards,
>
> Benoit TELLIER
>
> General manager of Linagora VIETNAM.
> Product owner for Team-Mail product.
> Chairman of the Apache James project.
>
> Mail: btell...@linagora.com
> Tel: (0033) 6 77 26 04 58 (WhatsApp, Signal)
>
>
> On May 21, 2025 2:44 PM, from Matt Pryor
> <pr...@international-presence.com>Good
> afternoon
>
> I'm in the process of getting the Guice-JPA server installed and running.
> The readme.adoc file says I need to create a keystore before doing
> anything.
> I did that and obviously had to enter a keystore password to secure it.
> When I run James it fails to read the keystore I created (as expected) as
> passwords don't match.
> Where is the password that it's using to access the keystore saved so I can
> edit it?
> Or should I use a standard password for this keystore?
> Also can I verify this is a separate keystore to the one used for TLS?
>
> Many thanks
> Matt
>
>
>
> Kind regards
> Matt Pryor
> Research and Development Manager
>
> The International Presence Group of Companies
> EMAIL: pr...@presencebpm.com
> URL: International-presence.com
>
> **** Please note my upcoming vacation dates: Monday 26th May - Friday 6th
> June 2025 inclusive ****
>
