# Re: java.security.Security.insertProviderAt() in appletviewer

Jan Luehe (Jan.Luehe@Eng)
Tue, 3 Feb 1998 12:02:35 -0800 (PST)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Jessica Mauvais: "Problem with SecureRandom call"
- Previous message: Jan Luehe: "Re: java.security.Security.insertProviderAt() in appletviewer"
- Maybe in reply to: Michael Hogan: "java.security.Security.insertProviderAt() in appletviewer"

    Date: Tue, 3 Feb 1998 12:02:35 -0800 (PST)

    From: Jan Luehe <Jan.Luehe@Eng>

    Subject: Re: java.security.Security.insertProviderAt() in appletviewer

    To: java-security@web1.javasoft.com, mhogan@iona.com

Mike:

My previous reply assumed you are using JDK 1.2.

If you are using JDK 1.1.x, you have to configure your provider
in the security properties file. Check

http://webwork.eng/products/jdk/1.1/docs/guide/security/CryptoSpec.html#Provider
Installing

for information on how to do this.

Jan

> > > I am trying to get an applet that makes SSL connections working in the
> > > appletviewer. The third party toolkit that I am using must be nominated
as
> > > a security provider using java.security.Security.insertProviderAt().
> > > However, the appletviewer's security manager denies me the right to do
this.
> > > Even if the applet is signed.
> > >
> > > Is there any way I can get around this restriction? Is there another
> > approach?
> >
> >
> > You need to add a "SecurityPermission" to your policy file, which may
> > look as follows:
> >
> > permission java.security.SecurityPermission "Security.insertProvider.*";
> >
> > Check
> >
> >
>
http://webwork.eng/products/jdk/1.2/docs/guide/security/CryptoSpec.html#Security
> >
> > for more information on how to do this.
> >
> >
> > Jan
> >
> >
> >
> >
>

- Next message: Jessica Mauvais: "Problem with SecureRandom call"
- Previous message: Jan Luehe: "Re: java.security.Security.insertProviderAt() in appletviewer"
- Maybe in reply to: Michael Hogan: "java.security.Security.insertProviderAt() in appletviewer"