Sun Microsystems 5.1.1 manual To generate a KeyStore

Page 30

Chapter 4

Section 4.2

Operating SSL

KeyStores and TrustStores

signing request (CSR). The CA is therefore trusted by the server-side application to which the eWay is connected.

Note: It is recommended to use the default KeyStore <c:\JavaCAPS>\logicalhost\is\domains\<MyDomain>\config\k eystore.jks where <c:\JavaCAPS> is the directory where the Sun Java Composite Application Platform Suite is installed and <MyDomain> is the name of your domain.

To generate a KeyStore

Use the following command:

keytool -keystore clientkeystore -genkey -alias client

You are prompted for several pieces of information required to generate a CSR. A sample key generation section follows:

Enter keystore password: seebyond What is your first and last name? [Unknown]: development.seebeyond.com

What is the name of your organizational unit? [Unknown]: Development

what is the name of your organization? [Unknown]: SeeBeyond

What is the name of your City of Locality? [Unknown]: Monrovia

What is the name of your State or Province? [Unknown]: California

What is the two-letter country code for this unit? [Unknown]: US

Is<CN=Foo Bar, OU=Development, O=SeeBeyond, L=Monrovia, ST=California, C=US> correct?

[no]: yes

Enter key password for <client>

(RETURN if same as keystore password):

If the KeyStore password is specified, then the password must be provided for the eWay. Press RETURN when prompted for the key password (this action makes the key password the same as the KeyStore password).

This operation creates a KeyStore file clientkeystore in the current working directory. You must specify a fully-qualified domain for the “first and last name” question. The reason for this use is that some CAs such as Verisign expect this properties to be a fully qualified domain name.

There are CAs that do not require the fully qualified domain, but it is recommended to use the fully-qualified domain name for the sake of portability. All the other information given must be valid. If the information can not be validated, a CA such as Verisign does not sign a generated CSR for this entry.

This KeyStore contains an entry with an alias of client. This entry consists of the Generated private key and information needed for generating a CSR as follows:

keytool -keystore clientkeystore -certreq alias client -keyalg rsa -file client.csr

HTTPS eWay Adapter User’s Guide

30

Sun Microsystems, Inc.

Page 29 Page 31
Image 30
Page 29 Page 31
Contents EWAY Https Adapter USER’S Guide Version Contents Http Settings Proxy Configuration Security Authentication Http OTD Method DescriptionsAdditional SSL Section Notes Verify hostname Connection Pool Settings Server Mode OperationRunning the Sample Running the Sample in SSL Mode Implementing the Https eWay JCD Sample ProjectsAbout Http and Https What’s in This ChapterAbout the Https eWay Http MessagesWeb Browser Cookies Sample Http Exchange in Client Mode GET and Post MethodsCookie Expiration Date Checking Sample Http Exchange in Server Mode Body HtmlWhat’s New in This Release Sample Input FormAbout This Document Text Conventions ScopeIntended Audience Https eWay JavadocRelated Documents Sun Microsystems, Inc. Web SiteDocumentation Feedback Installing the Https eWay Https eWay System RequirementsInstalling the Https eWay on an eGate supported system After you have installed eGate or eInsight, do the followingSteps to extract the Javadoc include After InstallationExtracting the Sample Projects and Javadocs Steps to extract the Sample Projects includeExport the Project Ican 5.0 Project Migration ProceduresInstall Java Caps Import the ProjectInstalling Enterprise Manager eWay Plug-Ins To View the eWay Alert Codes Viewing Alert CodesTo add plug-ins from the Enterprise Manager Https eWay Alert CodesHTTPCLIENTEWAY-CONNECT Overview of eWay OTDs Https Client OTDHttps Server OTD Http OTD Method DescriptionsInput Server Request Node Input Server Response Node Working with the Server OTDCollaboration Example SendResponse ExampleOperating SSL OverviewHacker Https eWayKeyStores KeyStores and TrustStoresGenerating a KeyStore and TrustStore Creating a KeyStore in JKS FormatTo generate a KeyStore Creating a KeyStore in PKCS12 Format Creating a TrustStore Using an Existing TrustStoreTrustStores To create a new TrustStoreSSL Handshaking Client ServerEWay Client EWay Server WebUsing the OpenSSL Utility Creating a Sample CA CertificateSigning Certificates With Your Own CA Windows OpenSSL.cnf File Example # SSLeay example properties fileChapter Section Operating SSL Using the OpenSSL Utility Copyright 1998-2001 The OpenSSL Project. All rights reserved Creating and Configuring the Https eWay Configuring the eWay Connectivity Map PropertiesTo configure the Https eWay properties To configure the Https Server eWay propertiesConfiguring the eWay Environment Properties Connectivity Map with Components ServerTo Configure the Environment Properties EWay Connectivity Map PropertiesHttps Server eWay Configuration Sections Include Configuring the Connectivity Map Https eWay PropertiesHttps eWay Configuration Sections Include Http eWay-HTTP SettingsHttp Server eWay-HTTP Server External Configuration EWay Environment PropertiesHttp Settings Environment Configuration-HTTP SettingsProxy Configuration Environment Configuration-Proxy ConfigurationName Description Required Value Proxy Port Proxy passwordSecurity Proxy UsernameAuthentication Environment Configuration-Security, AuthenticationEnvironment Configuration-Security, SSL Rovider Name Description Required Value Jsse Provider ClassCom.sun.net.ssl.internal.ssl.P Com.ibm.jsse.IBMJSSEProvidDescription Additional SSL Section NotesVerify hostname Required ValuesConnection Pool Settings Environment Configuration-Connection Pool SettingsAdditional information Setting Acceptor Threads Property for Https Server Mode Implementing the Https eWay Bpel Sample Projects EInsight Engine and ComponentsReceive Business Rule Designer Output Nodes Server Mode OperationHttps eWay With eInsight Node Name DescriptionReceive Business Rule Designer Output Nodes About the Https eWay eInsight Sample Projects Importing a Sample ProjectBuilding and Deploying the prjHTTPClientBPEL Sample Project Project OverviewGET Command GetSample.xml Project OperationsInput and Output Data Creating the OTD Post Command PostSample.xmlCreating a Project Sample DTD MultipleDataIn.dtdOTD Wizard Selection Include DTDs to Selected List Creating a Business Process OTD OptionsLogic of the Business Process Business Process Cases To create a Business ProcessCase Activity Result Business Process Icons Client Business Process With Link Business Rules Client Business Rule Designer First Link Business Rule Business Rule Designer Second Link Business Rule Business Rule Designer Third Link Business Rule Business Rule Designer Case 1 Business Rule Business Rule Designer Case 2 Business Rule Decision Gate Properties Dialog Box Case Creating a Connectivity Map To create a Connectivity MapDefining the Business Process Selecting External ApplicationsPopulating the Connectivity Map To select external applicationsBinding the eWay Components Steps required to bind eWay components togetherCreating an Environment Environment Editor envHTTPClientBPELCmHTTPClient Inbound File eWay Settings Configuring the eWaysConfiguring the Https eWay Properties CmHTTPClient Outbound File eWay SettingsConfiguring the Integration Server Creating and Activating the Deployment ProfileCreating and Starting the Domain Create and Start the DomainBuilding and Deploying the Project Running the SampleBuild the Project ƒ postBPELHTTPS Content of postBPELHTTPS.html is Building and Deploying the prjHTTPServerBPEL Sample ProjectProject Forms Server Sample Project Original FormServer Sample Project Input Form Next step is to create the Project’s Business Process Business Process Icons for Receive and Reply Business Process Icons With Server Business Rules Business Rule Designer Server Receive Business Rule Creating a Connectivity Map Connectivity Map With Components prjHTTPServerBPEL Creating an Environment Running the Sample in SSL Mode ƒ postBPELHTTPS.html input filePermission java.util.PropertyPermission * read, write Implementing the Https eWay JCD Sample Projects About the Https eWay JCD Sample ProjectsBuilding and Deploying the prjHTTPClientJCD Sample Project Https eWay Sample Project Java Collaboration Based SampleIn DTD SampleIn.dtd Creating the Collaboration Definition Java JcdHTTPClient Collaboration Definition Part 101 Connectivity Map With Components prjHTTPClientJCD 103 Building and Deploying the prjHTTPServerJCD Sample Project ƒ Project Overview onƒ postJCEHTTPS 106 107 JcdHTTPServer Collaboration Definition Connectivity Map With Components prjHTTPServerJCD 110 ƒ postJCEHTTPS.html input file 112 Index 114
Top Page Image Contents