JDK-4635083 : Enhanced security token integration
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-02-08
  • Updated: 2003-08-17
  • Resolved: 2003-08-17
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 tigerFixed
Related Reports
Relates :  
JDK-4894125 - Key(Pair)Generator and (Secret)KeyFactory need to perform error failover
Relates :  
JDK-4844847 - ByteBuffer APIs for JCA/JCE crypto
Relates :  
JDK-4856969 - Specify that ProviderException should be used for internal Provider errors
Relates :  
JDK-4856968 - Enhance the Provider class
Relates :  
JDK-4850423 - login facilities for hardware tokens
Description

Name: sl23568			Date: 02/07/2002



It should be possible to implement cryptographic JCA/JCE providers
that store cryptographic data or perform cryptographic operations
on hardware security tokens such as smart cards.

We will investigate whether the existing JCA/JCE APIs
are sufficient to support such operations cleanly,
or whether additional (or modified) APIs are required.


======================================================================
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b16
14-06-2004
EVALUATION Name: sl23568 Date: 02/07/2002 This feature has been added for Tiger release ====================================================================== Several RFEs have been created to track the individual issues. See 4844847, 4850376, 4850423, 4856968, and 4856969 for API changes and 4856966 for a new provider implementation. ###@###.### 2003-05-01 Marking fixed since the main body of work has now been putback. Additional improvements to the provider implementation will be made over time. Further tweaks to the JCA/JCE framework may be appropriate as well, see for example 4894125. ###@###.### 2003-08-12
12-08-2003