Presentation on theme: "SAML CCOW Work Item: Task 2 HL7 Working Group Meeting Phoenix – May 6-7 2008 Presented by: David Staggs, JD CISSP VHA Office of Information Standards."— Presentation transcript:
SAML CCOW Work Item: Task 2 HL7 Working Group Meeting Phoenix – May Presented by: David Staggs, JD CISSP VHA Office of Information Standards
2 Introduction: Project Scope Integration of CCOW with Security Assertion Markup Language (SAML) tokens. SAML allows the exchange of authentication and authorization data between security domains, that is, between an identity provider (a producer of assertions) and a service provider (a consumer of assertions).
3 TASK 2 Description and Use Case Establishing the user into context using a SAML assertion. USE Case: Security SOA where user authentication and authorizations are determined at network level. Authentication services provide universal SSO for all applications CCOW CM viewed authentication middleware for CCOW enabled applications and COTS products not SOA aware
4 Types of SAML Assertions Authentication: The specified subject was authenticated by a particular means at a particular time Attribute: The specified subject is associated with the supplied attributes Authorization Decision: A request to allow the specified subject to access the specified resource has been granted or denied
5 Notional Design: getting into context Authentication – source of the assertion Authentication Service authenticates the user directly SAML Authority passes identity/attribute assertions to Context Manager CM –assertion parsed for user id information Mapped to logon names from User Mapping Agent CM-Passed User to applications as normal ISSUE-How is Assertion Time to Live/Re- assertion managed?
8 Bearer Type Authentication Assertion The subject of the assertion is the bearer of the assertion, subject to optional constraints on confirmation using the attributes that may be present in the element. Example: The bearer of the assertion can confirm itself as the subject, provided the assertion is delivered in a message sent to https://www.provider.com/SAML/consumer before 1:37 PM GMT on May 9th, 2008, in response to a request with ID "_ ".