Release Notes - Development Kit for the Java Card Platform Version 3.0.1, Connected Edition

Print-friendly Version

Introduction

These release notes describe the development kit for the Java Card Platform, Version 3.0.1, Connected Edition, binary release.

Java Card technology combines a subset of the Java programming language with a runtime environment optimized for smart cards and similar small-memory embedded devices. The goal of Java Card technology is to bring many of the benefits of the Java programming language to the resource-constrained world of smart cards. The Java Card API is compatible with international standards such as ISO 7816, and industry-specific standards such as Europay, Master Card, and Visa (EMV).

Java Card platform version 3.0.1 is the latest evolution of Java Card technology. This development kit is based on the Version 3.0.1 of the Java Card Specifications.

For the first time, the Java Card platform is available in two editions, both of which are backward compatible with previous versions and share key security features:

• Classic Edition is based on an evolution of the Java Card Platform, Version 2.2.2, architecture. This edition targets more resource-constrained devices than the Connected Edition. Additional tools for the Classic Edition of the Java Card Platform, Version 3.0.1, are to be released at a later stage and are not covered by these notes.

• Connected Edition contains a new architecture compared to the Java Card technology released in version 2.2.2, which is now known as the "Classic Edition." The Connected Edition enables the integration of smart cards within IP networks and web services architectures. To do so, it features a significantly enhanced runtime environment and virtual machine (VM), and it includes new network-oriented features, such as support for Java Servlet APIs and Java Card applets with extended and advanced capabilities. These release notes are for the Connected Edition.

Back to top

Requirements

Platform

• Operating system. This release is targeted for use on the Microsoft Windows XP SP2 operating system.

Required Software

The following software must be installed for the Java Card development kit to work:

• Java Development Kit. The commercial version of Java Development Kit (JDK) version 6, Update 10 or later is required. You can download the supported JDK software, JDK 6 Update 10 or later, from http://java.sun.com/javase/downloads/index.jsp.
• GCC compiler. To build the VM, this release requires Minimal GNU for Windows (MinGW) version 5.1.3 or later. MinGW can be obtained from http://prdownloads.sourceforge.net/mingw. For information on MinGW go to http://www.mingw.org.
• Apache Ant. Apache Ant version 1.6.5 or later is required. Latest version of Apache Ant can be obtained http://ant.apache.org.

For use with the samples, the Firefox browser is considered a trusted client by the RI. Firefox is available at http://www.mozilla.com.

Note — Do not install any software in a directory that contains a space in its name. For example, do not install software in any subdirectory of c:\program files because of the space in the program files element.

Back to top

Contents of This Release

This binary release contains only binary code for the RI. Note that the Java Card specifications are not included in this release. The specifications must be downloaded separately.

This release contains features required to support classic applets, web applications, and extended Java Card applet applications on the card. Specifically, this release includes the following:

• Java Card runtime environment (cjcre.exe)
• Normalizer tool (normalizer.bat)
• OffCard Installer (installer.bat)
• Packager tool (jcpackager.bat)
• APDU tool (apdutool.bat)
• Debugging tool (debugproxy.bat)
• Romizer tool (romizer.bat)
• Converter tool (converter.bat)
• Sample applications
• User's guide for this release in Development Kit User's Guide for the Java Card Platform, Version 3.0.1, Connected Edition

Application Support

This release supports web applications and classic and extended Java Card applet-based applications. The card manager application, which is built in, allows the user to do the following:

• Load - Loading classic, web-based, and extended Java Card applet applications onto the card
• Create - Creating instances of classic, web-based, and extended Java Card applet applications
• List - Obtaining the list of loaded applications and created instances
• Delete - Deleting instances of classic, web-based, and extended Java Card applet applications
• Unload - Unloading classic, web-based, and extended Java Card applet applications from the card

Tools

• Normalizer (normalizer.bat) can be used for backward compatibility with classic applets
• OffCard Installer (installer.bat) is functional
• Packager (jcpackager.bat) can be used to both validate and create classic, web and extended Java Card applets applications
• Debugging tool (debugproxy.bat) can be used to debug applications in an IDE (such as the NetBeans IDE)
• APDU tool (apdutool.bat) can be used to send APDU scripts to the extended Java Card applet applications
• Romizer (romizer.bat) can be used to create custom ROM image files to create customized Java Card runtime environment (cjcre.exe)
• Converter (converter.bat) can be used to create classic applet application bundles

Java Card Runtime Environment (cjcre.exe) Features

• Support for the traditional, classic Java Card applets
• Package sealing
• Secure hosting of web applications on static and dynamically assigned ports
• SSL, HTTP and HTTPS connection support. (The SSL implementation is provided for reference  purposes and is not recommended for production use in devices.)
• On-card client application authentication
• Permission-based security
• Role-based security
• Code and context isolation between applications
• Transfer of object ownership support
• Transactions
• Extension library support
• SIO based services
• Events
• Restartable tasks
• Persistence
• Resource bundle support
• Evolutive Cryptography support
• Enhanced firewall support (including support for throwing exceptions across a firewall)
• Support for debugging using Java Card Debugger
• Preshared secret key support

Web Application Features

• All basic support for a typical web application (servlets, filters, listeners, etc.)
• BASIC, FORM and DIGEST authentication

Extended Java Card Applet Application Features

• All basic support for typical Extended Java Card Applet Application features (logical channels, etc.)
• T=0 and T=1 based APDU communication support
• APIs found in the Classic Edition

Back to top

Installation

For a more thorough description of the installation, contents and use of the development kit, see Development User's Guide, Java Card Platform, Version 3.0.1, Connected Edition included in the download bundle for this release.

An automatic installer tool can be used to unpack the download file containing this release. During download, you can choose to let the installer tool unpack the download file into a directory of your choice on your system or you can save the download file itself to your system.

Note — Do not install development kit software in any directory that has a space in its name. For example, on a Windows platform, do not install software in the c:\program files directory, or any subdirectory of c:\program files, because the program files element contains a space.

To install the Java Card development kit and associated software, follow these steps:

1. Install the JDK version 6, Update 10, or later. This JDK is available from: http://java.sun.com/javase/downloads/index.jsp.
2. Install Apache Ant version 1.6.5 or later. The latest version is available at: http://ant.apache.org/.
3. Install the GCC compiler. The compiler "Minimal GNU for Windows (MinGW), version 5.1.3" is required.  It is available at http://sourceforge.net/projects/mingw, while its installation information is at http://www.mingw.org.
4. Download the Java Card development kit. Download and store the development kit Java Archive (JAR) file in a directory of your choice.
5. Run the development kit installer or use the command line. Double click the JAR file on your system. If the JDK is installed correctly, the jar file is recognized as an executable jar and the automatic installer will launch to step you through the remainder of the installation process.
   
   Alternatively, you can use the command line to unpack the JAR file using the following command:
   
   java -jar Bundle-Filename
   
   Where Bundle-Filename is the downloaded development kit JAR file.

By default, the development kit is installed in c:\jcdk3.0.1_ConnectedEdition and its associated sub-directories. You can specify a different directory if you wish.

The directory c:\jcdk3.0.1_ConnectedEdition (or the alternate directory you specify during installation) is referred to as JC_CONNECTED_HOME in these release notes. When the development kit installation is complete, JC_CONNECTED_HOME contains the following:

Back to top

System Setup

Set System Variables and Paths

System variables and paths must be set before running the development kit. See the Development Kit User's Guide more details on how to set them. Note that if you choose to set the variables and paths each time you run the development kit rather than permanently in your system, you can place the appropriate commands in a batch file.

• JAVA_HOME. You must set the JAVA_HOME system variable to the JDK root directory before running the development kit.
  • To temporarily set JAVA_HOME from the command line, enter the command: set JAVA_HOME=c:\path before running the development kit. For example, if the Java platform software is stored in your c:\jdk6 directory, enter set JAVA_HOME=c:\jdk6 before running the development kit.
  
  
• JC_CONNECTED_HOME. You must set the  JC_CONNECTED_HOMEsystem variable to the directory in which the development kit is installed before running the development kit.  
• To temporarily set JC_CONNECTED_HOME from the command line, enter the command: set JC_CONNECTED_HOME=c:\path before running the development kit. For example, if the Java Card development kit is stored in your c:\jcdk3.0.1_ConnectedEdition directory, enter set JC_CONNECTED_HOME=c:\jcdk3.0.1_ConnectedEdition before running the development kit. 

• Apache Ant. You must set the ANT_HOME system variable to the Apache Ant directory before running the samples.
  
• To temporarily set ANT_HOME from the command line, enter the command: set PATH=c:\path before running the development kit. For example, if Apache Ant is stored in your c:\ant\apache-ant1.6.5 directory, enter set ANT_HOME=c:\ant\apache-ant1.6.5 before running the development kit.
  

• MinGW. You must set the path to the location of MinGW before running the development kit. Note that the path has to point to the \bin subdirectory of the MinGW installation directory where the gcc.exe file is located.
  • To temporarily set the path to MinGW, enter the command set PATH=c:\MinGW_path;%PATH%. For example, if MinGW is installed in c:\mingw, enter the command set PATH=c:\mingw\bin;%PATH% before running the development kit.

Configure the Java Card Runtime Environment for the Samples

Note that the Java Card RE (cjcre) implementation is not optimized for memory or performance and, therefore, requires more memory than an actual optimized implementation on a card. To run the samples provided with the development kit, the Java Card RE must be configured with at least 1M of RAM, 4M of EEPROM, and 4K of COR (Clear-On-Reset). These parameters can be provided to the Java Card RE using the Java Card RE command line as follows:

cjcre.exe -ramsize 1M -e2psize 4M -corsize 4K

For details see the Java Card RE command reference in the Development Kit User's Guide for the Java Card Platform, Version 3.0.1, Connected Edition.

Back to top

Uninstalling the Development Kit

To completely remove the development kit, simply delete the JC_CONNECTED_HOME directory and all of its contents.

Back to top

Known Bugs

This section describes known bugs and issues in the reference implementation.

NOTE: When running the Transit sample, you will need a User Name and PIN to authorize the remote admin. In the user guide's procedure "Run the Transit Sample" within Step #5, "Run the POSWEB sample application," there is a Sub-step #f.  After clicking the "AUTHORIZE" button in that step, you will need to enter the User Name as "owner-admin" and the PIN as "8888".

Bug ID	Description
6836385	SecurityException is thrown during an attempt to access shareable service in constructor or init
6841620	ECDSA Signature.init fails after card reset
6834466	resources from ext. libs should be visible to other ext. libst (regardless the order of libs)
6843228	ECDSA Signature - incorrect transactional behavior
6840273	applet is not installed if exception is thrown after register()
6842527	JCSystem.getAppletShareableInterfaceObject(JCSystem.getAID(), ..) throws SecurityException
6836643	IllegalAccessError is not detected during loading of the modules
6833322	JCint.setInt does not set all bytes correctly
6833320	ArrayLogic.arrayFillGenericNonAtomic works incorrectly
6840918	CLEAR_ON_DESELECT array becomes an CLEAR_ON_RESET array after card reset
6798109	Methods EventRegistry.unregister() don't unregister listeners by relative URI
6783969	Register and unregister methods don't throw IAE as specified
6843219	Listener registered for relative URI isn't notified of event with the same canonicalized URI
6762416	Implementation returns wrong status code while redirecting to secure port
6796195	java.security.AccessControlException is thrown instead of IllegalArgumentException
6835891	CLEAR_ON_DESELECT arrays cannot be created during application creation
6747078	To secure the platf. when using Basic/Digest auth., Authorization headers should be filtered out
6747080	Behavior of container when login-config is not defined must be aligned with the spec
6747084	Matching of <scheme> component of authenticator URIs with the web app auth-method must be relaxed
6753926	Authenticator URI should have a "realm-name" path component that should match web app realm name
6808246	Card Manager does not support protection domain names
6808317	EventRegistry.unregister must unregister only the entries regsitered by current app URI

Back to top

Where to Find Product Information and News

Visit the product web site at https://java-partner.sun.com/portal/service/ent/platform/javacardgroup This site has the most up-to-date information on the following:

• Product news and reviews
• Release notes and product documentation
• Technical support contact information

Back to top

Sending Feedback

We greatly appreciate your feedback on the specifications.