yes I surmised there was a dependency on the provider (in my case I was using 
BC as some of my Axis Projects were using BC)
In the case of the default Sun provider I'll use the default keystore of JKS

Thanks Chuck,
Martin--
--------------------------------------------------------------------------- 
This e-mail message (including attachments, if any) is intended for the use of 
the individual or entity to which it is addressed and may contain information 
that is privileged, proprietary , confidential and exempt from disclosure. If 
you are not the intended recipient, you are notified that any dissemination, 
distribution or copying of this communication is strictly prohibited.
--------------------------------------------------------------------------- 
Le présent message électronique (y compris les pièces qui y sont annexées, le 
cas échéant) s'adresse au destinataire indiqué et peut contenir des 
renseignements de caractère privé ou confidentiel. Si vous n'êtes pas le 
destinataire de ce document, nous vous signalons qu'il est strictement interdit 
de le diffuser, de le distribuer ou de le reproduire.
----- Original Message ----- 
From: "Caldarale, Charles R" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <[email protected]>
Sent: Sunday, March 04, 2007 5:13 PM
Subject: RE: valid keystore formats?


> From: Martin Gainty [mailto:[EMAIL PROTECTED] 
> Subject: valid keystore formats?
> 
> I have tried storetype=JCEKS but this always displays 
> "invalid keysotre format"

The default keystore format is jks (not case sensitive); support for
other formats is provided by additional JCE providers that could be
installed (but I don't know of any free ones).

From the keytool doc:
http://java.sun.com/j2se/1.5.0/docs/tooldocs/solaris/keytool.html

'There is a built-in default implementation, provided by Sun
Microsystems. It implements the keystore as a file, utilizing a
proprietary keystore type (format) named "JKS". It protects each private
key with its individual password, and also protects the integrity of the
entire keystore with a (possibly different) password.

'Keystore implementations are provider-based. More specifically, the
application interfaces supplied by KeyStore are implemented in terms of
a "Service Provider Interface" (SPI). That is, there is a corresponding
abstract KeystoreSpi class, also in the java.security package, which
defines the Service Provider Interface methods that "providers" must
implement. (The term "provider" refers to a package or a set of packages
that supply a concrete implementation of a subset of services that can
be accessed by the Java Security API.) Thus, to provide a keystore
implementation, clients must implement a "provider" and supply a
KeystoreSpi subclass implementation, as described in How to Implement a
Provider for the Java Cryptography Architecture.'

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received this in error, please contact the sender and delete the e-mail
and its attachments from all computers.

---------------------------------------------------------------------
To start a new topic, e-mail: [email protected]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to