JavaFAQ Home » 

There are two other cases to consider:

• The application server profile is the enterprise profile and the server key pair is already in a PKCS#12 file. If there is already an entry in the store with alias s1as, all you have to do is perform step 4 as described in "When the Enterprise Profile is Used" to delete the original entry:

                 certutil -D -n s1as -d $AS_NSS_DB 
  
  

  Then perform step 5 to import the new s1as.pfx file into the NSS store:

                    pk12util -i s1as.pfx -d $AS_NSS_DB 
  
  

  If there is no entry in the store with alias s1as, simply perform step 5.

• The application server profile is the developer profile and the server key pair is already in a PKCS#12 file. In this case, all you need to do is perform step 5 as described in When the Enterprise Profile is Used to delete the original s1as entry. Then use the pkcs12import utility to import the PCKS#12 file into the GlassFish keystore:

                 pkcs12import.sh -file s1as.pfx -alias s1as 
       -keystore keystore.jks -storepass changeit 
       -pass <exp_password>
  
  

  where <exp_password> is the password that was used when the PKCS#12 file was exported, for example, changeit.

  You can find the pkcs12import utility in the pkcs12import package, which you can download from the XWSS downloads page in Project Metro

For More Information

To learn more about SSL with GlassFish see SSL and CRL Checking with GlassFish v2.

Also see the following resources:

• Using JAX-WS-Based Web Services with SSL
• Glassfish with ECC
• Securing Web Applications in Java EE 5
• Configuring Security in GlassFish
• Installing and Configuring SSL Support in the Sun Java System Application Server
• Authentication (Java EE Blueprints)
• Enterprise Java Bean over SSL
• Key Management and PKCS#11 Tokens in Sun Java System Application Server 8.1
• No more 'unable to find valid certification path to requested target'

About the Author

Kumar Jayanti is a staff engineer at Sun Microsystems and works in the Web Technologies and Standards team. In his current role, Kumar is the lead for the XML and Web Services Security implementation and has also recently taken over responsibility for the GlassFish security module. He has been involved with the web services security effort at Sun since early 2004. Kumar holds an M.Tech degree in Computer Science from IIT Mumbai, India. His areas of interest include distributed computing, CORBA, XML, web services, and security.

Previous Page: When the Cluster Profile is Used

Page 1: Keys and Certificates
Page 2: GlassFish v2 Profiles
Page 3: Enabling the GlassFish v2 Application Server as an SSL Server
Page 4: When the Cluster Profile is Used
Page 5: Two other cases to consider

Custom Search