1 / 9

Architecture & Integration: CP v3.1

Architecture & Integration: CP v3.1. Client(s) Netscape/IE 4.0+. 3.x Platforms: Windows NT sp5(6a)/Solaris 2.8. Http.1 Multi-threading SSL accelerators. iWS. CP objects Java (JRE 1.3). IIOP. Java Method Calls. HTTP ‘packets’. Java Servlet Engine (Java Servlet API). C O R B A.

sonora
Télécharger la présentation

Architecture & Integration: CP v3.1

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Architecture &Integration: CP v3.1

  2. Client(s) Netscape/IE 4.0+ 3.x Platforms: Windows NT sp5(6a)/Solaris 2.8 • Http.1 • Multi-threading • SSL accelerators iWS CP objects Java (JRE 1.3) IIOP Java Method Calls HTTP ‘packets’ Java Servlet Engine (Java Servlet API) C O R B A Call Methods Include Statements iDS (LDAP) PSS MYSQL 3.22 128-bit encryption RC4 Algorithm OS File System - User/Group - ACL - Auth. - ‘hashed’EAS credentials [DocTemplate System] Example User Secrets: External email credentials CPIP credentials * Encrypted using login password credentials

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

  4. Campus Pipeline Email Integration

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

  6. Integration

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

  8. 1. User clicks link (containing external system destination URL) to the CPIP servlet. 2. CPIP makes authentication (& create user if necessary) requests to external system, using the supplied* authentication URL or create URL. 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. 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. 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. Campus Pipeline Integration Protocol

  9. Summary of Technical Benefits • 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

More Related