Security and Trust Services APIs for Java 2 Platform, Micro Edition Version 1.0 Reference Implementation Installation Guide Sun Microsystems, Inc. 4150 Network Circle Santa Clara, California 95054 U.S.A.
Copyright © 2004 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S.
Contents Preface 1. v Installing the SATSA Reference Implementation Locating and Downloading Supporting Software Setting System Variables Installing the SATSA Packages 2 2 3 Contents of the Reference Implementation 3 Running the SATSA 1.0 Reference Implementation Starting the MIDP 2.0 Emulator 4 Starting the Java Card Emulator 4 SATSA 1.0 Configuration Files Glossary Index 4 6 The internal.config File The system.
iv SATSA Installation Guide • July 2004
Preface This document describes how to install the Security and Trust Services APIs for the Java 2™ Platform, Micro Edition 1.0 Reference Implementation. Who Should Read This Guide This Installation Guide should be read by J2ME developers working with the Security and Trust Services APIs 1.0 Reference Implementation. Before You Read This Guide In order to fully use the information in this document, you must have thorough knowledge of the topics discussed in these guides: ■ Java Card Platform, Version 2.
How This Guide Is Organized Chapter 1 describes the supporting software needed to install the SATSA 1.0 Reference Implementation, how to test if the SATSA 1.0 installation is successful, and information about SATSA 1.0 configuration. Typographic Conventions vi Typeface Meaning Examples AaBbCc123 The names of commands, files, and directories; on-screen computer output Edit your .login file. Use ls -a to list all files. % You have mail.
Related Documentation Application Title Release Notes Security and Trust Services APIs Reference Implementation: Release Notes Accessing Sun Documentation Online The Source for Java Developers web site enables you to access Java™ platform technical documentation on the Web: http://java.sun.com/reference/docs/index.html Sun Welcomes Your Comments We are interested in improving our documentation and welcome your comments and suggestions. Send us your comments at: http://java.sun.
viii SATSA Installation Guide • July 2004
CHAPTER 1 Installing the SATSA Reference Implementation The Reference Implementation for the Security and Trust Services APIs (SATSA) for Java 2 Platform, Micro Edition Specification provides an implementation of the four optional packages defined in that specification. These are: ■ SATSA-APDU - Defines an API to support communication with smart card applications using the Application Protocol Data Unit (APDU) protocol.
Locating and Downloading Supporting Software The default platform for the SATSA 1.0 Reference Implementation is the Windows 2000/x86 platform. The SATSA 1.0 Reference Implementation is based on the Mobile Information Device Profile (MIDP) 2.0 code base. Before downloading and installing the SATSA 1.0 RI distribution, you must have the following software installed and configured: ■ Java 2 Platform, Standard Edition (J2SE) SDK, version 1.4.2, or the Java 2™ runtime environment, version 1.4.2.
Installing the SATSA Packages The Security and Trust Services 1.0 Reference Implementation is based on the Mobile Information Device Profile (MIDP) version 2.0 code base. Therefore, no separate installation of MIDP 2.0 is required; everything you need is contained in the SATSA 1.0 RI distribution. To install the SATSA 1.0 Reference Implementation: 1. Copy the SATSA 1.0 RI distribution file, satsa-1_0.zip, into some location in your file system, for example, at the same level as your Java Card platform 2.2.
Running the SATSA 1.0 Reference Implementation Running the SATSA 1.0 Reference Implementation involves two steps: ■ Starting the MIDP 2.0 emulator ■ Starting the Java Card (CRef) emulator Starting the MIDP 2.0 Emulator The SATSA 1.0 Reference Implementation is based on the MIDP 2.0 code base. To start the MIDP 2.0 emulator that incorporates the SATSA API, do the following: 1. Start up a Windows 2000 command shell window. 2. Type: C:\>%MIDP_HOME%\bin\midp This displays the MIDP 2.
In order to load this EEPROM image into CRef, do the following: 1. Start up a Windows 2000 command shell window. 2. Enter the following command into the command prompt, without line breaks: C:\>%JC_HOME%\bin\cref.exe -p -i %MIDP_HOME%\bin\jc_eeprom_image In the command line above, the should be one of the ports specified in the com.sun.midp.io.j2me.apdu.hostsandports property in the internal.config file. (For more information on the internal.config file, see “The internal.
SATSA 1.0 Configuration Files The SATSA 1.0 Reference Implementation contains two configuration files that, under most circumstances, can be left as-is and do not need to be altered or changed. These files are the following: ■ The internal.config File ■ The system.config File Both of these configuration files are found in the directory: %MIDP_HOME%\lib The internal.config File The internal.config file contains several MIDP 2.0 implementation-specific parameters.
The optional internal.config file parameters are: ■ keygen - specifies that a key be generated. Setting this parameter to false specifies that no key be generated. ■ opaquesig - specifies that opaque signatures be used. Setting this parameter to false does not allow the use of opaque signatures. ■ certsig - specifies that a certificate signature be used. Setting this parameter ro false does not allow the use of certificate signatures. The default SATSA 1.
8 SATSA Installation Guide • July 2004
Glossary AES Advanced Encryption Standard. The successor to the DES algorithm. It has a fixed block size of 128 bits and a key size of 128, 192, or 256 bits. APDU Application Protocol Data Units. A protocol used to define the structure of data messages exchanged between smart cards and smart card readers. CLDC Connected Limited Device Configuration. In conjunction with MIDP, provides the Java runtime environment for wireless and handheld devices. DES J2ME J2SE Java Card JCP Data Encryption Standard.
RI SATSA SE 10 Reference Implementation. A software package created to illustrate the concepts and APIs provided in a programming specification. Security and Trust Services APIs. A set of four J2ME optional packages that provide communication protocols, such as APDU and JCRMI, and security capabilities, such as PKI and encryption, for ensuring secure transactions between J2ME programs and a security element. Security Element.
Index C Configuration, 6 CRef, 5 D Downloading Supporting Software, 2 I internal.config File, 6 J Java 2, Standard Edition, 2 Java Card, Development Kit, 2 S SATSA Reference Implementation, 3 Supporting Software, Downloading, 2 system.
12 SATSA Installation Guide • July 2004
