Given by Tom Haupt at Security Meeting ASC on 15 March 99. Foils prepared 26 March 99
Outside Index
Summary of Material
Gateway and Proposed Security Architecture |
Outside Index Summary of Material
Services |
User Modules |
PSE |
Front-End |
OO |
Front-End |
User Space Definition and Task Specification |
Metacomputing Services |
Back-End Resources |
Master Server (Gatekeeper) |
Slave Server |
Slave Server |
User Context |
Application Context |
Module |
Slave Server Proxy |
Administrator |
(human) |
Client |
(Web Browser) |
Web Server |
Gateway Server |
keberized environment |
back-end resources |
middle-tier resources |
user 2 |
user 1 |
TGT |
TGT |
Akenti |
Architecture/Overview |
1 |
2 |
3 |
4 |
5 |
1. Browser -- Web Server -- Gatekeeper |
2. Gatekeeper -- User Context |
3. Module -- Module (across address spaces) |
4. Module -- Middle-Tier Service |
5. Module -- Back-End Service |
SECIOP |
Front End Applet |
https |
authentication |
& authorization |
Gatekeeper |
delegation |
Stakeholders |
HPCC resources |
GSSAPI |
GSSAPI |
Layer 1: secure Web |
Layer 2: secure CORBA |
Layer 3: Secure access to resources |
Policies defined by resource owners |
https (SSL) |
AKENTI |
CORBA security service |
GSSAPI (Globus) |
WebFlow Server |
IOR published as html doc |
WebServer |
1. Authentication |
2. Authorization 3. sessionID |
4. Fork process: |
{telnet client; user context} |
5. Return applet and sessionID |
WebFlow Server |
User Context (sessionID) |
telnet |
https |
WebServer |
1 |
2 |
WebFlow Server |
User Context (sessionID) |
WebServer |
html; servlets |
3 |
WebFlow Server |
User Context (sessionID) |
WebServer |
html; servlets |
"Slave server" |
3 |
Admin Context |
WebFlow Server |
User Context (sessionID) |
WebServer |
html; servlets |
"Another Context" |
4 |
Admin Context |
WebFlow Server |
User Context (sessionID) |
WebServer |
html; servlets |
"Another Context" |
Single Security Domain |
Secure Communications |
Authentication |
Client |
User |
Encryption |
Audit |
Authorization |
Server |
Encryption |
Credentials |
Object |
Adapter |
ORB |
A principal is authenticated once by ORB and given a set of credentials, including one or more roles, privileges, and an authenticated ID. |
An authenticated ID is automatically propagated by a secure ORB; it is part of the caller context |
Principal |
Credentials |
Current |
Client |
Server |
set_credentials |
get_attributes |
authenticate |
No delegation
|
Simple delegation
|
Composite delegation
|
Client |
Target |
Client |
Target |
Client |
Target |
Client |
Target |
Object |
IIOP |
Based on a trusted ORB model: you must trust that your ORB will enforce the access policy on the server resource |
The ORB determines: if this client on behalf of this principal can do this operation on this object |
Server uses Access Control Lists (ACL) to control user access |
Principal |
Role |
Rights |
Operation |
Mary Thompson, http://www-itg.lbl.gov/security/Akenti/DOE2000/sld014.htm |
WebServer |
html; servlets |
Admin Context |
WebFlow Server |
User Context (sessionID) |
"Another Context" |
5 |
Context |
GRAM |
Gatekeeper |
Job Manager |
Modified telnetd: |
take keberos ticket instead of password |
keberos ticket |
In order to run WebFlow over Globus there must be at least one WebFlow node capable of executing Globus commands, such as globusrun |
Jobs that require computational power of massively parallel computers are directed to the Globus domain, while other jobs can be launched on much more modest platforms, such as the user's desktop or even a laptop running Windows NT. |
Bridge between WebFlow and Globus |