aspose file tools*
The moose likes Security and the fly likes Algorithm not find but listed in the available algorithm of the security provider Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Security
Bookmark "Algorithm not find but listed in the available algorithm of the security provider" Watch "Algorithm not find but listed in the available algorithm of the security provider" New topic
Author

Algorithm not find but listed in the available algorithm of the security provider

Dominique Righetto
Greenhorn

Joined: Nov 27, 2007
Posts: 12

Hello,

I'm facing a strange issue...

During a test, i have listed the algorithms supported by all the security provider (SC) installed. There cases where a algorithm is listed as supported by a SC but when i try to get a instance of this to used it, the jvm throw a "NoSuchAlgorithmException"....

I didn't understand because the provider indicate that the algorithm is supported...

My environment informations are Java SE JDK 1.5.0_14 under Linux and Windows 2003 Server.

Thanks in advance for you light

Best regards,

Dom


Dominique Righetto
SCJP5/SCWCD5/SCBCD5
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 41874
    
  63
Post the code that shows that the algorithm exists but which is then unable to use it.


Ping & DNS - my free Android networking tools app
Dominique Righetto
Greenhorn

Joined: Nov 27, 2007
Posts: 12

This is the code that is used :
Ulf Dittmer
Marshal

Joined: Mar 22, 2005
Posts: 41874
    
  63
The most likely reason is that the first parameter to Cipher.getInstance is not an algorithm, but a transformation. A transformation contains a mode and a padding in addition to the algorithm; some can do without either of those, but most can't. See http://download.oracle.com/javase/1.5.0/docs/guide/security/jce/JCERefGuide.html#AppA for more information.
Dominique Righetto
Greenhorn

Joined: Nov 27, 2007
Posts: 12

After some tests (in a web app. deployed under Tomcat) it seems that the problem occurs when i update the application with a new war....I think that i can be a JVM Security provider update problem....
All theses are hypothesis
 
Don't get me started about those stupid light bulbs.
 
subject: Algorithm not find but listed in the available algorithm of the security provider