Sun Microsystems 5.1.1 manual About the Https eWay, Http Messages, Web Browser Cookies

Page 8

Chapter 1

Section 1.2

Introducing the HTTPS eWay

About the HTTPS eWay

HTTPS

HTTPS (hypertext transfer protocol over secure socket layer—or HTTP over SSL) is a Web protocol that encrypts and decrypts user page requests as well as the pages that are returned by the Web server. HTTP uses port 443 instead of HTTP port 80 in its interactions with the lower layer TCP/IP. SSL uses a 40-bit encryption key algorithm, which is considered an adequate level of encryption for commercial exchange.

When an HTTPS request is sent by a browser—usually by clicking a link that begins with https://—the client browser encrypts the request and sends it to the Web server. The acknowledgement sent by the Web server is also sent using encryption, and is decrypted by the client browser.

1.2About the HTTPS eWay

The HTTPS eWay enables eGate Integrator to communicate with client and server applications over the Internet using HTTP, either with or without SSL.

1.2.1HTTP Messages

An HTTP message has two parts: a request and a response. The message header is composed of a header line, header fields, a blank line, and an optional body (or data payload). The response is made up of a header line, header fields, a blank line, and an optional body (or data payload). HTTP is a synchronous protocol, that is, a client makes a request to a server and the server returns the response on the same socket.

1.2.2Web Browser Cookies

A cookie is an HTTP header, which is a key-value pair in the header fields section of an HTTP message.

The Set-Cookieand Cookie headers are used with cookies. The Cookie-requestheader is sent from the server in request for cookies on the client side. An example of a Cookie- request header is:

Set-Cookie: sessauth=44c46a10; expires=Wednesday, 27-Sep-2006 03:59:59 GMT

In this example, the server requests that the client store the following cookie:

sessauth=44c46a10

Everything after the first semi-colon contains additional information about the cookie, such as the expiration date. When the eWay sees this header, it extracts the cookie sessauth=44c46a10 and returns it to the server on subsequent requests. The eWay prepends a cookie header to the HTTP request, for example:

Cookie: sessauth=44c46a10

Each time the eWay sends a request to the same server during a session, the cookie is sent along with the request.

HTTPS eWay Adapter User’s Guide

8

Sun Microsystems, Inc.

Image 8
Contents EWAY Https Adapter USER’S Guide Version Contents Additional SSL Section Notes Verify hostname Http Settings Proxy Configuration Security AuthenticationHttp OTD Method Descriptions 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 ChapterWeb Browser Cookies About the Https eWayHttp Messages Cookie Expiration Date Checking Sample Http Exchange in Client ModeGET and Post Methods Sample Http Exchange in Server Mode Body HtmlWhat’s New in This Release Sample Input FormAbout This Document Scope Intended AudienceText Conventions Https eWay JavadocDocumentation Feedback Related DocumentsSun Microsystems, Inc. Web Site 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 followingAfter Installation Extracting the Sample Projects and JavadocsSteps to extract the Javadoc include Steps to extract the Sample Projects includeIcan 5.0 Project Migration Procedures Install Java CapsExport the Project Import the ProjectInstalling Enterprise Manager eWay Plug-Ins Viewing Alert Codes To add plug-ins from the Enterprise ManagerTo View the eWay Alert Codes 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 and TrustStores Generating a KeyStore and TrustStoreKeyStores Creating a KeyStore in JKS FormatTo generate a KeyStore Creating a KeyStore in PKCS12 Format Using an Existing TrustStore TrustStoresCreating a TrustStore To create a new TrustStoreSSL Handshaking EWay ClientServer 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 PropertiesConfiguring the Connectivity Map Https eWay Properties Https eWay Configuration Sections IncludeHttps Server 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 ConfigurationProxy password SecurityName Description Required Value Proxy Port Proxy UsernameEnvironment Configuration-Security, SSL AuthenticationEnvironment Configuration-Security, Authentication Name Description Required Value Jsse Provider Class Com.sun.net.ssl.internal.ssl.PRovider Com.ibm.jsse.IBMJSSEProvidAdditional SSL Section Notes Verify hostnameDescription Required ValuesAdditional information Connection Pool SettingsEnvironment Configuration-Connection Pool Settings Setting Acceptor Threads Property for Https Server Mode Implementing the Https eWay Bpel Sample Projects EInsight Engine and ComponentsServer Mode Operation Https eWay With eInsightReceive Business Rule Designer Output Nodes 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 OverviewInput and Output Data GET Command GetSample.xmlProject Operations Post Command PostSample.xml Creating a ProjectCreating the OTD Sample DTD MultipleDataIn.dtdOTD Wizard Selection Include DTDs to Selected List Creating a Business Process OTD OptionsLogic of the Business Process Case Activity Result Business Process CasesTo create a Business Process 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 MapSelecting External Applications Populating the Connectivity MapDefining the Business Process To select external applicationsBinding the eWay Components Steps required to bind eWay components togetherCreating an Environment Environment Editor envHTTPClientBPELConfiguring the eWays Configuring the Https eWay PropertiesCmHTTPClient Inbound File eWay Settings CmHTTPClient Outbound File eWay SettingsConfiguring the Integration Server Creating and Activating the Deployment ProfileCreating and Starting the Domain Create and Start the DomainBuild the Project Building and Deploying the ProjectRunning the Sample ƒ 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