Presentation is loading. Please wait.

Presentation is loading. Please wait.

Architecture & Integration: CP v3.1. 3.x Platforms: Windows NT sp5(6a)/Solaris 2.8 iWS Client(s) Netscape/IE 4.0+ Java Servlet Engine (Java Servlet API)

Similar presentations


Presentation on theme: "Architecture & Integration: CP v3.1. 3.x Platforms: Windows NT sp5(6a)/Solaris 2.8 iWS Client(s) Netscape/IE 4.0+ Java Servlet Engine (Java Servlet API)"— Presentation transcript:

1 Architecture & Integration: CP v3.1

2 3.x Platforms: Windows NT sp5(6a)/Solaris 2.8 iWS Client(s) Netscape/IE 4.0+ Java Servlet Engine (Java Servlet API) HTTP ‘packets’ CP objects Java (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 Methods Include Statements PSS Example User Secrets: External email credentials CPIP credentials * Encrypted using login password credentials 128-bit encryption RC4 Algorithm MYSQL 3.22 Http.1 Multi-threading SSL accelerators

3 Identification and Authentication Services (IAS) External Authentication Services (EAS) Message Protection Services (MPS) Access Control Services (ACS) Core Cryptographic Services (CCS) Campus Pipeline Security

4 Campus Pipeline Email Integration

5 Campus Pipeline iPlanet Calendar Server WCAP Berkley DB WCAP Email LDAP HTTP XSL/XML Users Subscriptions associations Calendars Events Campus Pipeline Calendar Integration

6 Integration

7 Client HTTP SCT Event Service HTTP LDAPLDAP Event ‘listener’ Client Events XML Batch Initializes LDAP Data Repository Event interface: JMS or CORBA/IDL Integration Protocol Data Integration with SCT

8 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. 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. 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. 2. CPIP makes authentication (& create user if necessary) requests to external system, using the supplied* authentication URL or create URL.

9 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


Download ppt "Architecture & Integration: CP v3.1. 3.x Platforms: Windows NT sp5(6a)/Solaris 2.8 iWS Client(s) Netscape/IE 4.0+ Java Servlet Engine (Java Servlet API)"

Similar presentations


Ads by Google