JDK-4856969 : Specify that ProviderException should be used for internal Provider errors
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 1.2.1,1.3.0_01,5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic,solaris_10,windows_2000
  • CPU: generic,x86
  • Submitted: 2003-05-01
  • Updated: 2017-05-16
  • 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 Availabitlity Release.

To download the current JDK release, click here.
Other
5.0 tigerFixed
Related Reports
Relates :  
Description
In JCA/JCE providers that are implemented on top of hardware token, any communication with that token may result in an error. For example, imagine a Smartcard based provider using a card that is physically removed from the reader in the middle of an operation. Or assume we want to store a key on the token, but there is insufficient memory, for example due to other threads concurrently creating objects.

The JCA/JCE APIs currently do not specify how to handle this situation. We plan to amend the specification of Provider to state that ProviderException (or a subclass) should be used for this purpose (ProviderException is an existing subclass of RuntimeException). Also, update the specification of ProviderException to explicitly mention internal errors.

This work is part of Tiger TOO 4635083.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b16
2004-06-14

WORK AROUND
2004-06-11

SUGGESTED FIX
2004-06-11

PUBLIC COMMENTS
2004-06-10

EVALUATION Will fix. ###@###.### 2003-05-01
2003-05-01