Architecture &Integration: CP v3.1

3.x Platforms: Windows NT sp5(6a)/Solaris 2.8

iWS

Client(s)Netscape/IE 4.0+

Java ServletEngine

(Java Servlet API)

HTTP ‘packets’

CP objectsJava (JRE 1.3)IIOP

Java Method Calls

C O R B A

iDS(LDAP)

- User/Group - ACL- Auth.- ‘hashed’EAS credentials

OS File System[DocTemplate System]

Call MethodsInclude Statements PSS

Example User Secrets:External email credentialsCPIP credentials* Encrypted using login password credentials

128-bit encryptionRC4 Algorithm

MYSQL 3.22

• Http.1• Multi-threading• SSL accelerators

• Identification and Authentication Services (IAS)• External Authentication Services (EAS)• Message Protection Services (MPS)• Access Control Services (ACS)• Core Cryptographic Services (CCS)

Campus Pipeline Security

Campus Pipeline Email Integration

CampusPipeline

iPlanetCalendarServer

WCAP

Berkley DB

WCAP

Email LDAP

HTTP

XSL/XML

•Users•Subscriptions•associations

•Calendars•Events

Campus Pipeline Calendar Integration

Integration

Client HTTP

SCT

EventService

HTTP

LDAP

Event ‘listener’

Client

Events

XML Batch InitializesLDAP Data Repository

Event interface: JMS or CORBA/IDL

Integration Protocol

Data Integration with SCT

Campus Pipeline Integration Protocol

1. User clicks link (containing

external system destination URL) to the CPIP servlet.

5. The external system establishes its user session, and redirects the browser to the original destination URL. The external system’s content is framed under the CP toolbar.

CPIPProtocol

3. External system authenticates

(and creates the user if necessary) and sends a pickup URL in the login response, which will help establish a session between the browser and the external system.

ExternalWeb

Application

CPIPConnector

4. CPIP extracts the pickup URL from the login response, and redirects the browser to the pickup URL, to establish the session. The pickup URL contains the original destination URL.

CampusPipeline

2. CPIP makes authentication (& create user if

necessary) requests to external system, using the supplied* authentication URL or create URL.

• Open, standard platform with proven infrastructure

• Proven Integration with Administrative Databases

• Proven Integration Protocol for single sign-on, session management and UI integration for all existing and future systems and applications • Centralized data and system administration via web based console and distributed access controls

• World class technical services and consulting

Summary of Technical Benefits