JDK-4393624 : Add getInstance(String, Provider) to JCE engine classes
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: javax.crypto
  • Affected Version: unknown
  • Priority: P3
  • Status: Closed
  • Resolution: Fixed
  • OS: solaris_7
  • CPU: generic
  • Submitted: 2000-11-30
  • Updated: 2001-08-08
  • Resolved: 2001-01-16
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
1.4.0 betaFixed
Related Reports
Relates :  
Relates :  
Description
    Java Cryptography Architecture is a pluggable framework. This means
    users can plug in different JCA providers in their environment.
    Currently, registered security providers are available to all applications
    running on the same VM instance. And one must register a security
    provider before using it. In order to register a security provider,
    one has to have approriate permissions or update the java.security
    file - this becomes an issue in deployment. Many users have found 
    that it would be very useful if an application/applet can access a 
    provider within its own space (note: not making that provider available 
    to other applications running on the same VM instance) without any 
    special security permissions.

    This method has already been added for the existing engine classes
    in J2SE. This RFE adds the method to the JCE engine classes:

       javax.crypto.Cipher
       javax.crypto.KeyAgreement
       javax.crypto.Mac
       javax.crypto.KeyGenerator
       javax.crypto.SecretKeyFactory
       javax.crypto.ExemptionMechanism

        

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: merlin-beta FIXED IN: merlin-beta INTEGRATED IN: merlin-beta VERIFIED IN: merlin-beta2
01-09-2004

EVALUATION sharon.liu@eng 2000-12-21 Yes, we should make the JCA/JCE APIs consistent.
21-12-2000