GSS-API authentication/BC may not be signed by a trusted party

"Cote, Jean-Claude" <[email protected]>
Newsgroups gmane.comp.java.sshtools.user
Message-ID <[email protected]>
Hi,

I'm working on grid technology and more specifically with globus and the
Java CoG kit.
There is no GSI (which is based on GSS-API) enabled Java ssh terminal yet
available to I'm trying to build one. I figured I could add GSI
authentication to the sshterm applet.

I'm running into difficulties regarding JCE. In my code I make use of
"org.globus.gsi.OpenSSLKey.decrypt()" from the cog-jglobus.jar, but when I
do so I get an error  message saying "The provider BC may not be signed by a
trusted party".

Now I have successfully used this code in my own signed applet before. This
applet loads the cog-jglobus.jar signed by me and the jce-jdk13-120.jar
signed by Bouncy Castle. It also prompts me to trust both entities.

In my opinion if the sshterm applet used the jce-jdk13-120.jar signed by
Bouncy Castle instead of having the code packaged into
SSHTermApplet-jdk1.3.1-dependencies-signed.jar my globus code would work.

Do you have any suggestions or recommendation regarding this issue?

Thanks!
Jean-Claude Cote
High Performance Computing / Calcul de haute performance
National Research Council Canada / Conseil national de recherches Canada
www.grid.nrc.ca
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.