# What's the end user process for granting access to a signed applet in JDK 1.2

Kurt Seidel (kurt.seidel@att.com)
Fri, 26 Jun 1998 14:31:45 -0400

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: huy_d1@verifone.com: "setting system class path"
- Previous message: Mike Burati: "Re: Desperately seeking JDK1.1.x Signature help!!!"

    Date: Fri, 26 Jun 1998 14:31:45 -0400

    From: Kurt Seidel <kurt.seidel@att.com>

    To: java-security@java.sun.com

    Subject: What's the end user process for granting access to a signed applet in JDK 1.2

I've got a pretty important question.

We're building a network-based address book application for use with
advanced telephony services, and as a real fan of Java, I'd like to
implement the Web interface in Java. However, in doing so, I'll need to
make use of signed applets to make connections to other machines, as
well as reading and writing to the client's local disk. To maintain
browser independence, I'm considering using the Java Plugin, combined
with JDK 1.1 and/or JDK 1.2 signed applets. The problem is, the end-user

experience for using JDK 1.1 signed applets is unacceptable. Here, it
seems that I'd have to tell my end user's (non-computer type people at
home potentially) to download the JDK, and instruct them on how to use
javakey to create or update their own identitydb.obj file. Get real!
This is just not feasible. The other option is send my end users an
identity.obj file that I've created, and ask them to copy it onto their
systems. Well, if someone else does this too, doesn't mine get wiped
out? This really seems like an unworkable end-user model.

To me, it seems that Netscape's model (object signing and capabilities
API) is ideal for end users. In this case when a signed applet is
loaded, the user is simply presented with a dialog asking them if they
wish to grant permission to the signer of the certificate for the
operations requested. This a workable end-user model. But, in order to
maintain browser independence, I'd like to be able to use a workable
model from SUN.

My question is:
1) Is my understanding of SUN's JDK 1.1 signed applet end-user scenario

correct? Or is there a more reasonable approach that I'm missing.

2) Can you tell me, or where (specifically - I've been looking all day)

can I find information on exactly what the end user scenario will be for

JDK 1.2 signed applets. It might be worth the wait if this one is more
reasonable. From what I've seen so far, I understand that policies can
be set up on an enterprise level, etc., but I really want to know
exactly what the typical non-PC literate home customer will have to go
through to grant access to a JDK 1.2 signed applet.

I influence development and technology decisions for a fairly large
organization here, so please do your best to fill me in on this ASAP.
Thank you very much.

Kurt D. Seidel
kurt.seidel@att.com

- Next message: huy_d1@verifone.com: "setting system class path"
- Previous message: Mike Burati: "Re: Desperately seeking JDK1.1.x Signature help!!!"