1 / 22

Gateway

Gateway. Building Secure Web Portals for Scientific Computing. Marlon Pierce School of Computational Science and Information Technology Florida State University. Overview. Design Goals and Constraints System Architecture Three-tiered system Security Considerations

kareem
Download Presentation

Gateway

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. Gateway Building Secure Web Portals for Scientific Computing Marlon Pierce School of Computational Science and Information Technology Florida State University

  2. Overview • Design Goals and Constraints • System Architecture • Three-tiered system • Security Considerations • What security do we need? • Three-tiered security system

  3. Project Goals • Provide seamless access to HPC resources from the user’s web browser. • Hide underlying complexities of environment behind a point-and-click interface. • Use platform and language independent tools to build distributed infrastructure. • Java, CORBA, XML

  4. Funding and Deployment • Project funded by DoD Modernization Program (PET). • Deployment targeted for ASC and ARL MSRCs. • Requirement: Compatible with existing security infrastructure • Kerberos and SecurID

  5. Project Design Overview • Three-tiered architecture • Browser-based, dynamic front-end • Scalable, distributed middle-tier • Heterogeneous backend resources • Three major constituents: • Problem Solving Environment for users (OSC) • WebFlow (NPAC) • HPC resources (ASC)

  6. PSE Design Goals • User interface with three toolkits • Problem Description Toolkit • Describe problem in scientific terms • Archive old sessions • Code Toolkit • Assist user in creating job requests • Analysis Toolkit

  7. PSE Decision Containers User Context Marlon’s Chemistry Project Problem Context 30 Particles, Energy, Crystal Structure Session Context Run Gausssian on SP2 with In.dat

  8. WebFlow • CORBA-based distributed components. • Each user has a personal slave server. • Master server acts as a gatekeeper, maintaining proxies of all child objects. • WebFlow provides general methods for managing containers (contexts). • WebFlow can be extended with modules (ContextManager, submitJob, Charon)

  9. WebFlow Context Hierarchy Master Server (Gatekeeper) Slave Server Proxy Slave Server Application Context Module Slave Server T. Haupt User Context

  10. Back-End Resources • High performance computers • Batch queues • Globus schedular • Mass storage devices • Databases (through JDBC) • Chemistry, visualization software • Everything else

  11. Gateway Communication I Apache Tomcat Web Server HPC Resources, Mass Storage, DBs HTTP(S) PSE Browser ORB WebFlow ORB krsh, krcp

  12. CORBA Security Service Overview • Provides generic interfaces to standard security services • Authentication • Integrity and Confidentiality • Delegation • Implementations can be built over specific security mechanisms. • GSS mechanisms like Kerberos • SSL

  13. CORBA Security Services Security Specification API Vendor-Supplied Interface Security Implementation

  14. Gateway Communication II HPC Resources, Mass Storage, DBs Apache Tomcat PSE Browser ORB HTTP WebFlow Servers Charon ORB ORB SECIOP ORB SECIOP krsh, krcp

  15. Secure Gateway Login Process • User gets forwardable Kerberos ticket at beginning of the day with kinit. • User starts personal WebFlow slave server that registers with the master. • Slave runs with user’s id. • User starts Charon Client, which uses his/her TGT to authenticate to the WebFlow master server.

  16. Charon: Client-Server Security • Charon application intercepts all requests to predetermined port on user’s computer. • Requests are wrapped with WebFlow methods and tunneled to web server with SECIOP. • Server masquerades as client’s localhost. • Different browsers on same machine distinguished with session cookies.

  17. Charon II • Charon extracts user’s name from his credentials. • This is used to set a server-side cookie. • PSE servlets use the info in the cookie for access control.

  18. PSE-WebFlow Communication • A WebFlow client ORB runs in a servlet. • Master’s ORB is declared static. • All PSE servlets access WebFlow methods directly. • PSE accesses slave server indirectly through master. WebFlow Client PSE Servlets JVMs Slave WFS

  19. Middle Tier Security • Client does not talk directly to slave. • Indirect invocation through master’s proxy. • Master and slave run with different ids. • Need delegation and mutual authentication. Client Master Slave Proxy Module

  20. Security: WebFlow to HPCs • User requests are passed from master to appropriate slave. • Slave makes external call with krsh, krcp to HPC resources. • The slave is created by the user with forwardable credentials, so external calls use existing security mechanism.

  21. NPAC/FSU/MSU Geoffrey Fox Tomasz Haupt Erol Akarsu Choonhan Youn OSC Ken Flurchick Jan Labanowski Armen Ezekielian Adiron Software Polar Humenn Acknowledgements

  22. Further Information • www.gatewayportal.org (coming soon) • www.osc.edu/~kenf/sciPortal • www.erc.msstate.edu/~haupt/WebFlow

More Related