You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Amit Pande <Am...@veritas.com.INVALID> on 2023/11/03 00:48:32 UTC

RE: [External] RE: Java 9+ and custom JCE/JSSE providers

Hello Cris,

The system property can take an URL.

java.security.properties=<URL>.

However, my quick testing suggests the protocol (file:/ ) isn't needed.

Also, perhaps worth reading the effects of "=" and "==" while using this property.

https://bugs.openjdk.org/browse/JDK-7133344
https://github.com/frohoff/jdk8u-dev-jdk/blob/master/src/share/lib/security/java.security-linux

Thanks,
Amit

-----Original Message-----
From: Berneburg, Cris J. - US <cb...@caci.com.INVALID>
Sent: Thursday, November 2, 2023 3:41 PM
To: Tomcat Users List <us...@tomcat.apache.org>
Subject: [External] RE: Java 9+ and custom JCE/JSSE providers


CAUTION: This email originated from outside the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. If you believe this is a phishing email, use the Report to Cybersecurity icon in Outlook.



Amit

> -Djava.security.properties=file:/path/to/java_security_properties_file

That "file:" prefix looks like Spring syntax.  Is the prefix needed on the JVM command line?

--
Cris Berneburg
CACI Senior Software Engineer

-----Original Message-----
From: Amit Pande <Am...@veritas.com.INVALID>
Sent: Tuesday, October 31, 2023 10:23 AM
To: Tomcat Users List <us...@tomcat.apache.org>
Subject: Java 9+ and custom JCE/JSSE providers

EXTERNAL EMAIL - This email originated from outside of CACI. Do not click any links or attachments unless you recognize and trust the sender.





Hello,

I am in the process of updating https://github.com/amitlpande/tomcat-9-fips page for version later than Java 8.

Ran into an issue:


  1.  Was looking the configure the additional bouncy castle providers in the Java install itself by:
     *   Modifying the java.security file to add providers.
     *   Place the jars in the Java'e lib/ext directory.
  2.  However, from Java 9+, the lib/ext directory is no longer present (https://docs.oracle.com/javase/9/migrate/toc.htm#JSMIG-GUID-2C896CA8-927C-4381-A737-B1D81D964B7B)
  3.  The alternate I attempted was to place the additional provider jars in Tomcat's lib directory.
  4.  Create a java security properties file with:
                    security.provider.1=org.bouncycastle.jcajce.provider.BouncyCastleFipsProvider
                    security.provider.2=org.bouncycastle.jsse.provider.BouncyCastleJsseProvider fips:BCFIPS
                   security.provider.3=sun.security.provider.Sun
                   ssl.KeyManagerFactory.algorithm=PKIX
                   ssl.TrustManagerFactory.algorithm=PKIX

  1.  Launch Tomcat with JVM option -Djava.security.properties=file:/path/to/java_security_properties_file
  2.  However, I noticed that these BC providers weren't getting loaded.






    I see a comment from Chris here -  https://www.mail-archive.com/users@tomcat.apache.org/msg137824.html
"I don't see any place in Tomcat to specify the JSSE provider. Perhaps we should expose that to the administrator in some way."

Not sure if it's relevant here.

But wanted to know if there is any way to configure Tomcat for Java 9+ with custom JSSE/JCE providers (with just config change) ? Maybe I missed something?

Also, FWIW, I was able get the FIPS configuration for Java 11, 17 with Tomcat 9, by registering a custom listener and adding providers there. Will soon update the https://github.com/amitlpande/tomcat-9-fips for detailed steps.

Thanks,
Amit




________________________________

This electronic message contains information from CACI International Inc or subsidiary companies, which may be company sensitive, proprietary, privileged or otherwise protected from disclosure. The information is intended to be used solely by the recipient(s) named above. If you are not an intended recipient, be aware that any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify the sender immediately.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org