For testing purposes a {@link nl.nikhef.slcshttps.TestSURFCA#main(String[]) main()} method is provided by {@link nl.nikhef.slcshttps.TestSURFCA}, which shows {@link nl.nikhef.slcshttps.PKCS12Https} and {@link nl.nikhef.slcshttps.SURFCAHttps}. It can be called using e.g.:

  java -D... -jar slcshttps_jdk15_v0.1.jar "https://www.nikhef.nl/~msalle/cert/showcert?nohtml=1"

• nl.nikhef.slcshttps.CERT_URL
  Contains the URL used to POST the {@link nl.nikhef.slcshttps.crypto.CSR} to, and get the Certificate from as response. Used by {@link nl.nikhef.slcshttps.SURFCAHttps}.
• nl.nikhef.slcshttps.AUTH_URL
  The webbrowser goes to either the value of this property plus the CSR hash if it starts with http(s):// or uses it as a postfix to the value of nl.nikhef.slcshttps.CERT_URL and then adds the CSR hash. Used by {@link nl.nikhef.slcshttps.SURFCAHttps}.
• nl.nikhef.slcshttps.comm
  Used to determine whether to use stdio or popups for user communication by classes {@link nl.nikhef.slcshttps.SURFCAHttps}, {@link nl.nikhef.slcshttps.PKCS12Https} and {@link nl.nikhef.slcshttps.trust.TrustManagerImpl}. For SURFCAHttps another way to communicate is used by the {@link nl.nikhef.slcshttps.gui.SURFCAInitDialog} which hence also ignores this setting by implementing and empty {@link nl.nikhef.slcshttps.SURFCAHttps.SURFCACommunicator}. Other applications using this package probably want to provide their own implementations of these communicator interfaces {@link nl.nikhef.slcshttps.SURFCAHttps.SURFCACommunicator}, {@link nl.nikhef.slcshttps.PKCS12Https.PKCS12Communicator} and {@link nl.nikhef.slcshttps.trust.TrustManagerImpl.TrustCommunicator}.
  values: stdio popup
• nl.nikhef.slcshttps.https
  Whether to use {@link javax.net.ssl.HttpsURLConnection} or {@link nl.nikhef.slcshttps.trust.HttxURLConnection} (which is firefox-like in its asking for confirmation about invalid server certificates). The default is to use "mask", which means it's behaving as if only HttxURLConnection is used, but in practise also HttpsURLConnection is setup for using the client side certificates. Value "both" does practically the same except for the {@link nl.nikhef.slcshttps.gui.CAPanel}/{@link nl.nikhef.slcshttps.gui.SerialPanel} classes: value "both" will show for both HttpsURLConnection and HttxURLConnection which certificate is in use for client side authentication, while value "mask" will only show HttxURLConnection (although both will be set).
  values: https httx both mask
• nl.nikhef.slcshttps.acknowledge
  Whether to show confirmation on succesful importing of certificate.
  values: true false