Notes on jdk.certpath.disabledAlgorithms

Brent Putman putmanb at georgetown.edu
Mon Jan 23 17:40:16 EST 2017



On 1/23/17 5:00 PM, Brent Putman wrote:
>>         <argLine>-Djava.security.properties=${project.basedir}/java.security-overrides</argLine> 
>
> That works, but as I mentioned somewhere else (where?), that's
> probably sub-optimal b/c we then have to keep that file updated with
> any new/changed stuff going forward, and/or the tests would no longer
> function as a canary to whatever stuff they change wrt the JRE
> defaults in the future..

Actually, for future reference and to correct my earlier statements... 
Upon reviewing the java.security comments, it's not quite that bad. 
Specifying that prop exactly that way (with 1 equals sign, per usual)
allows you to override individual properties *only* since it logically
appends to the existing file.  So the concern about having to replicate
the whole file contents isn't true.

You *can* override the whole file with 2 equals signs.  A little funky...


# An alternate java.security properties file may be specified
# from the command line via the system property
#
#    -Djava.security.properties=<URL>
#
# This properties file appends to the master security properties file.
# If both properties files specify values for the same key, the value
# from the command-line properties file is selected, as it is the last
# one loaded.
#
# Also, if you specify
#
#    -Djava.security.properties==<URL> (2 equals),
#
# then that properties file completely overrides the master security
# properties file.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20170123/e5521585/attachment.html>


More information about the dev mailing list