You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2007/07/12 12:45:04 UTC
[jira] Assigned: (AXIS2-2944) Allow https connection without a
keystore
[ https://issues.apache.org/jira/browse/AXIS2-2944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-2944:
----------------------------------------
Assignee: Saminda Wishwajith Abeyruwan
> Allow https connection without a keystore
> -----------------------------------------
>
> Key: AXIS2-2944
> URL: https://issues.apache.org/jira/browse/AXIS2-2944
> Project: Axis 2.0 (Axis2)
> Issue Type: New Feature
> Components: transports
> Affects Versions: 1.2
> Reporter: Michael Davis
> Assignee: Saminda Wishwajith Abeyruwan
> Priority: Minor
>
> Normally when we connect over https, if the server sends us a certificate that is not well known, we have to specify a keystore using system properties:
> System.setProperty("javax.net.ssl.trustStore","path to keystore" );
> System.setProperty("javax.net.ssl.trustStorePassword","apache");
> We should allow clients to either provide a certificate by some other means, such as hard-coding the bytes, or allow the client to disregard the certificate and trust the server. This is because clients are sometimes deployed on systems where the developers have no access to the file system and therefore cannot configure the keystores.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org