TeraGrid 08 The Third Annual TeraGrid Conference

TeraGrid 08 The Third Annual TeraGrid Conference
Tom Scavo, Jim Basney , Terry Fleury, Von Welch National Center for Supercomputing Applications June 9–13, 2008

Tutorial: Building Science Gateways
TeraGrid 08 Tom Scavo, Jim Basney , Terry Fleury, Von Welch National Center for Supercomputing Applications June 9, 2008

Birds-of-a-Feather Session: Attribute-based Auditing and Authorization for Science Gateways

Science Gateways Working Group Session

Tutorial: Building Science Gateways
TeraGrid 08 Tutorial: Building Science Gateways Mon, 8:00am–12:00pm Birds-of-a-Feather Session: Attribute-based Auditing and Authorization for Science Gateways Wed, 5:30–6:30pm Poster Session: A Federated Identity Model for Science Gateways Wed, 6:30–8:30pm Science Gateways Working Group Session Thu, 3:00–4:30pm

Grid Security Infrastructure (GSI)

GSI relies heavily on X.509 proxy certificates
Grid Authentication Traditionally, grid authentication has been via trusted X.509 identity certificates GSI relies heavily on X.509 proxy certificates A proxy cert is a short-lived certificate signed by the user’s identity certificate Multiple GSI authentication mechanisms: GSI Transport (SSL/TLS) GSI Secure Message (WS-Security) GSI Secure Conversation (WS-SecureConversation)

The Classic Grid Use Case
A non-browser user issues a proxy certificate and initiates a grid request on her own behalf.

Issue a Proxy Certificate
grid-proxy-init X.509 End Entity Cred Issuer: Certification Authority Subject: End User X.509 Proxy Credential Issuer: End User Subject: End User+ Key Key myproxy-logon

Classic GSI GT4 Client GT4 Server Java WS Container Globus WS Client
Globus Web Service X.509 proxy certificate X.509 proxy credential Gridmap Key

Identity-based Access Control
The distinguished name (DN) in the proxy certificate is used as a basis for coarse-grained access control If the subject DN is in an access control list called a gridmap file, access is allowed A gridmap file also maps DNs to usernames Associated with each DN are zero or more local usernames GRAM, for example, requires a local account in which to run a job request

The gridmap has a flat file format: DN → [user0, user1, …, usern-1]
Gridmap File The gridmap has a flat file format: DN → [user0, user1, …, usern-1] The gridmap has dual functions: Authorization Policy Username Mapping Policy A single gridmap file serves both functions Identity-based gridmap files trade off flexibility and scalability for simplicity DN1 username1 DN2 username2 …

GridShib-enabled GSI

GridShib software allows Globus Toolkit and Shibboleth to interoperate
GridShib Project The goal of the GridShib Project is to introduce attribute-based authorization to Globus-based grids GridShib software allows Globus Toolkit and Shibboleth to interoperate Classic GridShib (circa 2004–2005) pulls attributes from a Shibboleth Attribute Service The current emphasis is on browser users and attribute push, specifically, the TeraGrid Science Gateway Use Case

GridShib for Shibboleth GridShib CA GridShib SAML Tools
GridShib Software GridShib for GT Consumes X.509-bound SAML assertions issued by the GridShib CA or the GridShib SAML Tools. Issues SAML attribute queries to a Shibboleth IdP with GridShib for Shibboleth installed. GridShib for Shibboleth Responds to attribute queries from GridShib for GT. GridShib CA Issues short-lived X.509 credentials to browser users. GridShib SAML Tools Issue or requests SAML assertions and optionally binds these assertions to X.509 proxy certificates.

GS-ST is a SAML producer
GridShib SAML Tools The GridShib SAML Tools (GS-ST) are a standalone suite of Java-based client tools Binds a SAML assertion to an X.509 proxy certificate The same X.509-bound SAML token can be transmitted at the transport level or the message level (using WS-Security X.509 Certificate Token Profile) Includes the GridShib Security Framework, a Java API for producing and consuming X.509-bound SAML tokens GS-ST is a SAML producer

Easily installed and configured
GS-ST Features Easily installed and configured Binds arbitrary content (not just SAML) to a non-critical certificate extension Multiple output options (SAML, X.509 proxy credential, DER-encoded ASN.1) CLI with shell scripts (UNIX and Windows) Includes a Java API for portal developers Leverages the Globus SAML Library, an enhanced version of OpenSAML 1.1

Bind a SAML assertion to a non-critical X.509 v3 certificate extension
GS-ST Function Bind a SAML assertion to a non-critical X.509 v3 certificate extension We call this an X.509-bound SAML token

grid-proxy-init X.509 Proxy Credential X.509 Community Cred
Issuer: Science Gateway Subject: Science Gateway+ X.509 Community Cred Issuer: TeraGrid CA Subject: Science Gateway Key Key

gridshib-saml-issuer
grid-proxy-init X.509 Proxy Credential Issuer: Science Gateway Subject: Science Gateway+ X.509 Community Cred Issuer: TeraGrid CA Subject: Science Gateway Key X.509 Proxy Credential Issuer: Science Gateway Subject: Science Gateway+ X509v3 extension: : Key <saml:Assertion> <saml:NameID> trscavo </saml:NameID> </saml:Assertion> gridshib-saml-issuer Key

The SAML token is bound to a noncritical X.509v3 certificate extension
X.509-bound SAML Token GridShib SAML Tools produces X.509-bound SAML tokens, a new type of security token that enables attributed-based authorization in X.509-based Grids The SAML token is bound to a noncritical X.509v3 certificate extension X.509 Proxy Credential Issuer: Science Gateway Subject: Science Gateway+ X509v3 extension: : <saml:Assertion> <saml:NameID> trscavo </saml:NameID> </saml:Assertion> Key

WS-Security Token Profiles
OASIS WS-Security Technical Committee WSS X.509 Certificate Token Profile [1] WSS SAML Token Profile Globus implements the former We define a new token type: X.509-bound SAML Token An implementation of [1] automatically handles X.509-bound SAML tokens No new wire protocols are needed!

Security Tokens X.509 Token SAML Token http://gridshib.globus.org/
SOAP Envelope SOAP Envelope SOAP Header SOAP Header X.509 certificate SAML assertion SOAP Body SOAP Body

Security Tokens X.509-bound SAML Token X.509 Token SAML Token
SOAP Envelope SOAP Envelope SOAP Envelope SOAP Header SOAP Header SOAP Header X.509 certificate X.509 certificate SAML assertion SAML assertion SOAP Body SOAP Body SOAP Body

a SAML assertion to a proxy certificate and initiates a grid request
GridShib-enabled GSI A non-browser user binds a SAML assertion to a proxy certificate and initiates a grid request on her own behalf

GridShib for GT (GS4GT) is a plug-in for GT 4.x
GS4GT is compatible with both GT 4.0 and 4.2 GS4GT is an implementation of a Grid Service Provider, which is analogous to a Shibboleth Service Provider, but for X.509-based grids GS4GT is a SAML consumer Used together, GridShib SAML Tools and GridShib for GT enable attribute-based access control in Globus-based grids

Introduces attribute-based authorization into GT
GS4GT Features Introduces attribute-based authorization into GT Exposes a single comprehensive policy decision point called the GridShibPDP Implements an attribute push model Restricts access based on blacklists of IP addresses and/or name identifiers Provides attribute-based account mapping Supports optional gridmap short-circuiting Defines an attribute-based authorization policy language (in XML)

GridShib-enabled GSI GT4 Client GT4 Server http://gridshib.globus.org/
Java WS Container (with GridShib for GT) Globus WS Client GridShib SAML PIP Globus Web Service proxy certificate SAML GridShib SAML Tools proxy credential Security Context SAML Key end entity credential Logs Blacklist Policy Authz Policy Key

GS4GT Configuration Files
GridShib SAML Entity Map The SAML Entity Map maps SAML issuers to X.509 issuers A SAML issuer in this file is trusted The SAML Entity Map will be replaced by SAML Metadata (XML) A blacklist is a list of identifiers (SAML identifiers or subject DNs) A user whose identifier is on the blacklist will be denied access The flat file blacklist will be replaced by a database table entityID1 DN1 entityID2 DN2 … GridShib Blacklist Policy identifier1 identifier2 …

GridShib Mapping Policy
GS4GT Policy Files DN1 username1 DN2 username2 … Globus Gridmap file GridShib Mapping Policy GridShib Authz Policy <XML> <XML>

Two separate attribute-based policy files:
GS4GT Policy Files Two separate attribute-based policy files: Authorization Policy [A0, A1, …, Am-1] Username Mapping Policy [A0, A1, …, Am1-1] → [user0, user1, …, usern1-1] [A0, A1, …, Am2-1] → [user0, user1, …, usern2-1] … A single XML-based policy file may encapsulate both types of policies

Fine-grained, attribute-based authorization
Summary Fine-grained, attribute-based authorization Introduces X.509-bound SAML tokens Works at both the transport level or the message level No modifications to GT clients are required If the service is not GridShib-enabled, the X.509-bound SAML token is simply ignored

A Grid Authorization Model for Science Gateways

The Science Gateway Use Case
A browser user authenticates to a grid portal. The portal issues a proxy certificate and initiates a grid request on behalf of the user

Classic Science Gateway
A science gateway is a convenient intermediary between a browser user and a grid resource provider. Web Browser Web Authn Web Interface Java WS Container Webapp WS GRAM Client WS GRAM Service community credential community account Key Science Gateway Resource Provider

Each gateway is issued a community credential that uniquely identifies the gateway. Web Browser Web Authn Web Interface Java WS Container Webapp WS GRAM Client WS GRAM Service community credential community account Key Science Gateway Resource Provider

Resource providers associate the community credential with a local community account. Web Browser Web Authn Web Interface Java WS Container Webapp WS GRAM Client WS GRAM Service community credential community account Key Science Gateway Resource Provider

To submit a job, a browser user typically authenticates to the gateway by presenting a username and password. Web Browser Web Authn Web Interface Java WS Container Webapp WS GRAM Client WS GRAM Service community credential community account Key Science Gateway Resource Provider

The gateway then issues a short-lived proxy credential signed by its community credential. Web Browser Web Authn Web Interface Java WS Container Webapp WS GRAM Client WS GRAM Service community credential proxy credential community account Key Key Science Gateway Resource Provider

The gateway submits the job on the user’s behalf, authenticating as itself to the resource. Web Browser Web Authn Web Interface Java WS Container Webapp WS GRAM Client WS GRAM Service proxy certificate community credential proxy credential community account Key Key Science Gateway Resource Provider

The resource authenticates the gateway and maps the request to the community account based on the identity in the proxy certificate. Web Browser Web Authn Web Interface Java WS Container Webapp WS GRAM Client WS GRAM Service proxy certificate community credential proxy credential community account Key Key Science Gateway Resource Provider

After the job is executed, the result is returned to the browser user via the gateway web interface. Web Browser Web Authn Web Interface Java WS Container Webapp WS GRAM Client WS GRAM Service proxy certificate community credential proxy credential community account Key Key Science Gateway Resource Provider

Community Account Model: The Good
The Community Account Model simplifies the user experience simplifies gateway implementation and deployment simplifies gridmap file management at the RP A community credential is issued to each gateway A single community account is created at the RP The gateway issues proxy certificates and makes grid requests on behalf of the user

Community Account Model: The Bad
The community account model has some significant drawbacks, however: End user identity is unknown to the RP Course-grained access control at the resource (by design) Awkward approach to auditing and incident response In the event of an emergency, the RP is forced to disable all access to the community account Less than adequate accounting mechanisms All this can be traced to a single problem…

Community Account Model: The Ugly
All requests look exactly the same to the resource provider! If the gateway would only pass the user’s name and contact information to the resource provider, all previously mentioned problems would be solved

Grid Authorization Model
We describe a grid authorization model that significantly increases the information flow between a science gateway and a resource provider Extends the Community Account Model Asserts end user identity to the RP Permits fine-grained access control at the RP Provides strong auditing and effective incident response Allows dynamic blacklisting of problem accounts or runaway processes A lightweight approach that does not require new wire protocols or extensive new middleware infrastructure Complements existing SAML-based middleware infrastructure on today's campuses

Grid Authorization Model
The proposed model incorporates GridShib SAML Tools at the gateway and GridShib for GT at the resource provider Using GridShib SAML Tools, the gateway issues a SAML assertion containing the user's authentication context and attributes binds the SAML assertion to a proxy certificate signed by the community credential authenticates to the resource by presenting the SAML-laden proxy certificate

+ = <saml:Assertion> <saml:NameID> trscavo
X.509 Proxy Credential Issuer: Science Gateway Subject: Science Gateway+ <saml:Assertion> <saml:NameID> trscavo </saml:NameID> </saml:Assertion> + = Key X.509 Proxy Credential Issuer: Science Gateway Subject: Science Gateway+ X509v3 extension: : <saml:Assertion> <saml:NameID> trscavo </saml:NameID> </saml:Assertion> Key

GridShib-enabled Science Gateway
A browser user authenticates to a grid portal. The portal binds a self-issued SAML assertion to a proxy certificate and initiates a grid request on behalf of the user.

Grid Authorization Model for Gateways
An enhancement to the community account model increases the information flow between the gateway and the resource provider. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools community credential Key Science Gateway Resource Provider

A software component called GridShib SAML Tools is integrated into the gateway portal environment. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools community credential Key Science Gateway Resource Provider

Another software component called GridShib for GT is deployed at the resource provider. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools community credential Key Science Gateway Resource Provider

These two GridShib software components produce and consume Security Assertion Markup Language (SAML) tokens. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools community credential Key Science Gateway Resource Provider

Again the browser user authenticates to the gateway by presenting a username and password. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools community credential Key Science Gateway Resource Provider

This time the gateway uses the GridShib SAML Tools to issue an X.509-bound SAML token. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools proxy credential SAML Key community credential Key Science Gateway Resource Provider

The SAML token bound to the proxy certificate contains the name of the end user and other user attributes (e.g., ). Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service X.509 Proxy Credential Issuer: Science Gateway Subject: Science Gateway+ X509v3 extension: : username GridShib SAML Tools proxy credential SAML Key community credential Key <saml:Assertion> <saml:NameID> trscavo </saml:NameID> </saml:Assertion> Science Gateway Resource Provider Key

The gateway authenticates as itself to the resource provider, presenting the proxy certificate with bound SAML token. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service proxy certificate SAML username GridShib SAML Tools proxy credential SAML Key community credential Key Science Gateway Resource Provider

The GridShib SAML policy information point (PIP) extracts the SAML token from the proxy certificate, parses it, and writes the information to a log file. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service proxy certificate SAML username GridShib SAML Tools proxy credential SAML Key community credential Logs Key Science Gateway Resource Provider

The security information in the SAML token is also used to populate a SAML security context within the container. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service proxy certificate SAML username GridShib SAML Tools proxy credential Security Context SAML Key community credential Logs Key Science Gateway Resource Provider

The service compares the information in the security context to the blacklist, denying access if any request info is on the blacklist. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service proxy certificate SAML username GridShib SAML Tools proxy credential Security Context SAML Key community credential Logs Blacklist Policy Key Science Gateway Resource Provider

The service combines the information in the security context with its access control policy, allowing access if and only if policy is satisfied. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service proxy certificate SAML username GridShib SAML Tools proxy credential Security Context SAML Key community credential Logs Blacklist Policy Authz Policy Key Science Gateway Resource Provider

As before, after the service executes the job, the result is returned to the browser user via the gateway web interface. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service proxy certificate SAML username GridShib SAML Tools proxy credential Security Context SAML Key community credential Logs Blacklist Policy Authz Policy Key Science Gateway Resource Provider

GridShib-enabled Science Gateway
Simple installation and configuration of GridShib SAML Tools at the gateway Includes GridShib Security Framework Exposes both a command-line interface and a Java API End user identity and contact information (e.g., ) transmitted to RP Push much of the responsibility for auditing and incident response back onto the RP Big Advantage: No need to shut down the entire gateway in the event of an incident!

Subject name identifier: Authentication statement
User Attributes Gateway entityID: Subject name identifier: Authentication statement authentication method: urn:oasis:names:tc:SAML:1.0:am:password authentication instant: T12:10: IP address: Attribute statement isMemberOf attribute: group://gisolve.org/gisolve mail attribute:

GridShib-enabled Resource Provider
The end user and the end user’s contact information (and other attributes) are logged Effective auditing and incident response Blacklist an IP address or name identifier on demand Exposes a SAML security context Fine-grained, attribute-based access control

Virtual Organization Membership Service
Comparison with VOMS Virtual Organization Membership Service The most successful grid authorization model today VOMS binds X.509 attribute certificates (instead of SAML) to proxy certificates VOMS requires the requester to be the subject; VOMS will not issue an AC to a requester acting on behalf of the subject Therefore, a gateway can not call out to a VOMS server to obtain attributes for a user Conclusion: VOMS can not be used as a basis for gateway security

Integration with TeraGrid Central Database
Resource Provider Java WS Container (with GridShib for GT) The GridShib-enhanced community account model permits fine-grained access control and effective incident response at the resource. GridShib SAML PIP WS GRAM Service Security Context Logs Policy AMIE upload Security table GRAM audit table TGCDB

Resource Provider Java WS Container (with GridShib for GT) Since each request is now associated with a unique end user, we push job info to TeraGrid Central for improved auditing and accounting. GridShib SAML PIP WS GRAM Service Security Context Logs Policy AMIE upload Security table GRAM audit table TGCDB

Resource Provider Java WS Container (with GridShib for GT) First, the security context associated with each incoming request is captured in a security table. GridShib SAML PIP WS GRAM Service Security Context Logs Policy AMIE upload Security table GRAM audit table TGCDB

Resource Provider Java WS Container (with GridShib for GT) Likewise the disposition of every job request is captured in an enhanced GRAM audit table. GridShib SAML PIP WS GRAM Service Security Context Logs Policy AMIE upload Security table GRAM audit table TGCDB

Resource Provider Java WS Container (with GridShib for GT) An AMIE process joins these two tables and pushes an information packet to the TeraGrid Central Database. GridShib SAML PIP WS GRAM Service Security Context Logs Policy AMIE upload Security table GRAM audit table TGCDB

Resource Provider Java WS Container (with GridShib for GT) A gateway can query the TGCDB for individual accounting records, permitting fine-grained accounting at the gateway. GridShib SAML PIP WS GRAM Service Security Context Logs Policy AMIE upload Security table GRAM audit table TGCDB

Resource Provider Java WS Container (with GridShib for GT) TeraGrid adminstrators can query the TGCDB for aggregate accounting data for the purposes of NSF reporting and planning. GridShib SAML PIP WS GRAM Service Security Context Logs Policy AMIE upload Security table GRAM audit table TGCDB

Gateway Job Accounting
TeraGrid Resource Provider (RP) -No Changes required to AMIE -DAI provides virtualization for audit and accounting DBs GT4 Java Container Core Audit Table Core Deleg Audit Table Delegation Diagram courtesy of Stu Martin RFT Audit Table RFT Client / Gateway ** sudo Create Job Get EPR RM adapter Control Job with EPR MJFS Resource Manager RM log - Query Using Grid JID MEJS ** SEG GRAM Audit Table - Reply with Accounting record RM Accounting User Job(s) OGSA DAI GET UNIQUE USER ID + Local AMIE Accounting ** Locally convert EPR to Grid JID AMIE upload Central TG Accounting DB

Benefits of TGCDB Integration
The gateway can query the TGCDB (via OGSA-DAI) and implement local, fine-grained accounting mechanisms TeraGrid administrators can obtain aggregate accounting data for NSF reporting and planning

TeraGrid Deployment Strategy
GridShib SAML Tools at the Gateway GridShib for GT at the RP Integrate GS4GT into CTSS4 Integrate with TeraGrid Central Database Retrofit GRAM 4.0 Audit with end user identity Assist with the design and implementation of GRAM 4.2 Audit (in particular, the security table)

A Federated Identity Model for Science Gateways

Federated Identity The long term vision is to introduce federated identity at the science gateway Shibboleth, an open-source implementation of the SAML Browser Profiles, provides: Ubiquity Manageability Usability Security Since Shibboleth is based on SAML, our model complements existing campus infrastructure

Science Gateway Resource Provider
It is well-known that password management at the gateway is a significant administrative burden for both the gateway and the end user. Web Browser Web Authn Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools community credential Key Science Gateway Resource Provider

SAML Identity Provider
To avoid having to manage passwords at the gateway, we propose a federated identity solution on the browser-facing side of the gateway. Web Authn Web Browser SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools Science Gateway Resource Provider

A third-party Identity Provider on each campus manages user identity and credentials. Web Authn Web Browser SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools Science Gateway Resource Provider

The gateway, which is protected by a Service Provider, trusts the Identity Provider to authenticate the browser user. Web Authn Web Browser SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools Science Gateway Resource Provider

Since we’re already invested in SAML on the back end, we prefer an implementation of the standard SAML browser profiles (such as Shibboleth). Web Authn Web Browser SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools Science Gateway Resource Provider

Web Authn A browser user authenticates to their preferred campus Identity Provider instead of the science gateway. Web Browser SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools Science Gateway Resource Provider

SAML Assertion Web Authn The SAML Identity Provider issues a SAML token that the user transmits to the gateway via the browser. Web Browser SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools Science Gateway Resource Provider

SAML Assertion Web Authn The SAML Service Provider protecting the gateway consumes the SAML token in lieu of a username/password. Web Browser SAML Assertion SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools Science Gateway Resource Provider

SAML Assertion Web Authn The gateway issues a combined SAML token containing both campus attributes and local attributes. Web Browser SAML Assertion SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service username GridShib SAML Tools proxy credential SAML+ Key community credential Key Science Gateway Resource Provider

SAML Assertion Web Authn The gateway authenticates as itself to the resource provider, presenting the combined X.509-bound SAML token. Web Browser SAML Assertion SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service proxy certificate SAML+ username GridShib SAML Tools proxy credential SAML+ Key community credential Key Science Gateway Resource Provider

SAML Assertion Web Authn Since the gateway did not authenticate the end user directly, the resource provider must decide if it trusts the combined SAML token. Web Browser SAML Assertion SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service proxy certificate SAML+ username GridShib SAML Tools proxy credential Security Context SAML+ Key community credential Logs Key Science Gateway Resource Provider

SAML Assertion Web Authn In the case of federated identity, access control policy at the resource provider is more complex since a third security domain is involved. Web Browser SAML Assertion SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service proxy certificate SAML+ username GridShib SAML Tools proxy credential Security Context SAML+ Key community credential Logs Blacklist Policy Authz Policy Key Science Gateway Resource Provider

SAML Assertion Web Authn SAML Web Browser SSO closes the loop for complete end-to-end flow of security information Web Browser SAML Assertion SAML Service Provider Web Interface Java WS Container (with GridShib for GT) attributes Webapp WS GRAM Client GridShib SAML PIP WS GRAM Service proxy certificate SAML+ username GridShib SAML Tools proxy credential Security Context SAML+ Key community credential Logs Blacklist Policy Authz Policy Key Science Gateway Resource Provider

Federated Identity Model for Gateways
TeraGrid Science Gateway B C SAML Assertion X.509 proxy credential SAML Key X.509 proxy certificate SAML Shib-enabled Grid Portal GridShib-enabled Grid Client response response X.509 end entity credential GridShib-enabled Grid SP Key Browser A D SAML Request SAML Request X.509 Shibboleth SSO Service GridShib-enabled Attribute Service SAML Assertion SAML Assertion Shibboleth Identity Provider

Birds-of-a-Feather Session

Is your gateway infrastructure built on a JEE portal framework?
If so, which one? If not, what application server do you use?

If not, describe your security framework.
Is your gateway security framework built on the community credential model? If not, describe your security framework.

If not, is the community credential stored in the file system?
Do you use MyProxy? If not, is the community credential stored in the file system?

In your application server environment, how easy is it to obtain the following information:
Username Authentication instant IP address address Does your portal framework provide an API to obtain this information or do you have to query a database?

Does your gateway control its own DNS domain?
If not, what is the URL of your gateway? [relate this to "scope"]

Original Project PIs Developers Acknowledgments
Von Welch, Tom Barton, Kate Keahey, Frank Siebenlist Developers Rachana Ananthakrishnan, Jim Basney, Tim Freeman, Raj Kettimuthu, Terry Fleury, Tom Scavo The GridShib work was funded by the NSF National Middleware Initiative (NMI awards and ). Opinions and recommendations in this paper are those of the authors and do not necessarily reflect the views of NSF. The Science Gateway integration work is funded by the NSF TeraGrid Grid Integration Group through a sub-award to NCSA.

GridShib http://gridshib.globus.org/
Thank you! GridShib

TeraGrid 08 The Third Annual TeraGrid Conference

Similar presentations

Presentation on theme: "TeraGrid 08 The Third Annual TeraGrid Conference"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

TeraGrid 08 The Third Annual TeraGrid Conference

Similar presentations

Presentation on theme: "TeraGrid 08 The Third Annual TeraGrid Conference"— Presentation transcript:

Similar presentations

About project

Feedback