Release 10.1A: OpenEdge Getting Started:
Core Business Services

> ## Configuring and running SSL sessions

> When an SSL server and client have access to authenticating keys and certificates they can engage in SSL communications, which occurs in the context of an SSL session. Before starting them, you have to configure, code, or otherwise specify to the client and server that they must communicate using SSL as directed by certain SSL session properties. The mechanisms for doing this differ depending on the server and client type, but the functional and manageable properties of an SSL session are the same among all OpenEdge server types and among most OpenEdge client types. During an SSL session, clients that you program (Progress 4GL and Open Clients) can also access the identity of the SSL server they are talking with.

> The following sections describe these SSL session properties:

> - Configuring SSL server sessions

> - Configuring SSL client sessions

> - Accessing an SSL server’s X.500 Subject Name

> Each SSL session property has a functional name that differs slightly, depending on the component you are configuring and how you configure it. The possible mechanisms for specifying these properties include the:

> - Startup parameters (or switches) on the command line or in scripts.

> - Progress Explorer framework component property editors or component properties in the `ubroker.properties` file.

> - Connection parameters, object properties, and other appropriate internal code for SSL client or server components that you program yourself.

> The following sections describe the function of these SSL session properties using generic names and phrases and specify the mechanism that you can use to set them for each SSL server and client component.

> Note: The actual property settings in OpenEdge might be expressed differently depending on the actual property and the mechanism used to set it.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095