# Re: TrustManagerFactory/KeyManagerFactory algorithms

Kevin Regan (kevin@Differential.COM)
Thu, 12 Aug 1999 12:09:26 -0700 (PDT)

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Charlie Lai: "Re: RMI Permissions with applets"
- Previous message: Jeff Nisewanger: "Re: JSSE question"
- In reply to: Chandrakant Yemparala: "loading local applet"

    From: Kevin Regan <kevin@Differential.COM>

    Message-Id: <199908121909.MAA14955@Differential.COM>

    Subject: Re: TrustManagerFactory/KeyManagerFactory algorithms

    To: Jeff.Nisewanger@eng.sun.com

    Date: Thu, 12 Aug 1999 12:09:26 -0700 (PDT)

    In-Reply-To: <199908121821.LAA07286@shorter.eng.sun.com> from "Jeff Nisewanger" at Aug 12, 99 11:20:10 am

Thanks for the info. I notice the, for the KeyManagerFactory,
the "init" method takes a KeyStore and a password. It only seems
to work if I give it a KeyStore with only a single private key
in it. If I provide a KeyStore with multiple keys, I get an
unrecoverable key exception. Would it make sense to add an
"alias" argument to the init command to specify both the key
name and password that we are interested in.

Also, I've noticed that the Key and Trust manager factorys
return arrays of key and trust managers. What are these (I've
simply been passing them to the "init" method of the SSL Context.

Thanks,
Kevin

>
>
> > I've been playing around a bit with the JSSE and I've come
> > to the point where I would like to create an SSLContext.
> > However, first I need to instantiate a TrustManagerFactory
> > and a KeyManagerFactory. There are static factory methods
> > that take an algorithm name as a parameter. What are the
> > supported algorithm names? Also, what are the supported
> > protocol names to instantiated an SSLContext?
>
>
> This is documented in the file jsse1.0/doc/additional.html when
> you install the JSSE reference implementation. The names of the
> supported protocols for SSLContext are "SSL" and "TLS".
>
> You can also implement your own trust and key factories
> and ssl contexts by writing your own java.security.Provider and
> registering it as a security provider via the java.security.Security
> class. If you get an instance of the JSSE reference provider you can
> use the Provider methods to see how the implementation class properties
> are named. For example, an alternate implementation of a trust factory
> might support more sophisticated certificate validation services.
>
>
> Jeff
>
>

- Next message: Charlie Lai: "Re: RMI Permissions with applets"
- Previous message: Jeff Nisewanger: "Re: JSSE question"
- In reply to: Chandrakant Yemparala: "loading local applet"