DOCSLIB.ORG

IHE IT Infrastructure Technical Framework White Paper 2006-2007 Cross-Enterprise User Authentication (XUA)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
IHE IT Infrastructure Technical Framework White Paper 2006-2007 Cross-Enterprise User Authentication (XUA) ACC, HIMSS and RSNA Integrating the Healthcare Enterprise 5 IHE IT Infrastructure Technical Framework White Paper 2006-2007 For Public Comment 10 Cross-Enterprise User Authentication (XUA) 15 IHE ITI Technical Committee Editor: John F. Moehrke 20 Version 2.0 2006-08-15 IHE ITI White Paper Cross-Enterprise User Authentication ______________________________________________________________________________ 25 Contents 1 Introduction............................................................................................................................ 4 2 Background............................................................................................................................ 5 2.1 Identity Enabled Services ................................................................................................ 5 2.2 SAML Assertion.............................................................................................................. 6 30 3 Healthcare Use cases ............................................................................................................. 7 3.1 Assumptions .................................................................................................................... 7 3.2 Use Case Categories......................................................................................................... 8 3.2.1 User Authentication (0a/b/c)............................................................................................................................... 8 3.2.2 HL7 Export/Import (1a)....................................................................................................................................... 8 35 3.2.3 HL7 Query (1b)..................................................................................................................................................... 9 3.2.4 DICOM Export/Import (2a) ................................................................................................................................ 9 3.2.5 DICOM Query (2b) .............................................................................................................................................. 9 3.2.6 XDS – Provide and Register (3)......................................................................................................................... 9 3.2.7 XDS – Register (4) .............................................................................................................................................. 9 40 3.2.8 XDS – Query (5) ................................................................................................................................................. 10 3.2.9 XDS – Retrieve (HTTP Get – Application) (6)............................................................................................. 10 3.2.10 RID – Display (HTTP Get – Browser) (7) ................................................................................................ 10 3.2.11 Sue views note (XDS) (5, 6, 7).................................................................................................................... 10 4 Actors / Transactions........................................................................................................... 11 45 4.1 Example EHR with XDS and XUA grouping................................................................. 11 4.2 XUA Integration Profile Process Flow........................................................................... 12 4.2.1 Post-Generated Assertion.................................................................................................................................. 13 4.2.2 Pre-Generated Assertion.................................................................................................................................... 14 4.2.3 XDS Provide and Register Delegation Model............................................................................................... 15 50 4.3 Access Controls.............................................................................................................. 15 4.4 Audit Logs ..................................................................................................................... 16 5 Guidance............................................................................................................................... 17 5.1 Trust Relationship......................................................................................................... 17 5.2 Assertion Content.......................................................................................................... 17 55 5.3 Enhanced Client or Proxy Profile .................................................................................. 18 5.4 Web SSO Profile ............................................................................................................ 18 5.5 Web Services Profile ...................................................................................................... 18 5.6 HL7 Profile .................................................................................................................... 19 5.7 DICOM Profile .............................................................................................................. 19 60 6 Conclusion............................................................................................................................ 20 7 GLOSSARY.......................................................................................................................... 21 8 Referenced Standard............................................................................................................ 22 __________________________________________________________________________ Rev. 2.0: PC – 2006-08-15 2 Copyright © 2006: ACC/HIMSS/RSNA IHE ITI White Paper Cross-Enterprise User Authentication ______________________________________________________________________________ OPEN ISSUES:............................................................................................................................ 24 __________________________________________________________________________ Rev. 2.0: PC – 2006-08-15 3 Copyright © 2006: ACC/HIMSS/RSNA IHE ITI White Paper Cross-Enterprise User Authentication ______________________________________________________________________________ 65 1 Introduction IHE has defined a profile for Enterprise User Authentication (EUA) and Personnel White Pages (PWP) for use within an enterprise. The IHE is now defining transactions that cross enterprise boundaries, specifically the XDS profile and others that create an Affinity Domain. When transactions cross enterprise boundaries the mechanisms found in the EUA and PWP profile are 70 insufficient and often nonfunctional. To provide accountability in these cross enterprise transactions there is a need to identify the requesting user in a way that the receiver can make access decisions and proper audit entries. This white paper proposes a Cross-Enterprise User Authentication (XUA) profile that will provide the user identity in transactions that cross enterprise boundaries. Enterprises may choose 75 to have their own user directory and their own unique method of authenticating. To provide accountability in these cross enterprise transactions there is a need to identify the requesting user in a way that the receiver can make access decisions and proper audit entries. The IHE has decided to publish this white paper instead of a Profile at this time. Although the use of SAML 2.0 Assertions is viewed as appropriate, there is a lack of experience with SAML 80 to understand the need for a Profile. We may need to specify the SAML Assertion content beyond specifying the use of SAML 2.0. We may also need a more complete support for the pre- authorized SAML assertion for many IHE transactions. There is much work going on in OASIS, WS-I, and Liberty Alliance that should fill some of these gaps. We now must decide if we are going to develop profiles that are unique to Healthcare, or wait and leverage the near future 85 standards work. __________________________________________________________________________ Rev. 2.0: PC – 2006-08-15 4 Copyright © 2006: ACC/HIMSS/RSNA IHE ITI White Paper Cross-Enterprise User Authentication ______________________________________________________________________________ 2 Background Security protects assets from risks. Information security protects information assets from risks to confidentiality, integrity and availability. Only through a security risk assessment and mitigation plan, executed at each design level, will information assets be appropriately protected. IHE is 90 now evaluating all Profiles in the context of a risk assessment plan to assure that risks are managed in the proper priority and with proper means. For more information on applying risk assessment strategy see the IHE web site for a white paper on risk assessment. The IHE profiles available today provided for distributed accountability that is tied together through the use of node-to-node authentication between systems that agree to handle access 95 controls and audit trails. Access control policies are becoming more complex. Systems are often built on architectures that are loosely coupled such as n-tier web-services. The result is that the user is further away from the data. An enterprise can impose a single authentication technology and a single personnel directory. Multiple enterprises that participate in an affinity domain may
Load more

Recommended publications
  • Are3na Crabbé Et Al
    ARe3NA Crabbé et al. (2014) AAA for Data and Services (D1.1.2 & D1.2.2): Analysing Standards &Technologies for AAA ISA Action 1.17: A Reusable INSPIRE Reference Platform (ARE3NA) Authentication, Authorization & Accounting for Data and Services in EU Public Administrations D1.1.2 & D1.2.2– Analysing standards and technologies for AAA Ann Crabbé Danny Vandenbroucke Andreas Matheus Dirk Frigne Frank Maes Reijer Copier 0 ARe3NA Crabbé et al. (2014) AAA for Data and Services (D1.1.2 & D1.2.2): Analysing Standards &Technologies for AAA This publication is a Deliverable of Action 1.17 of the Interoperability Solutions for European Public Admin- istrations (ISA) Programme of the European Union, A Reusable INSPIRE Reference Platform (ARE3NA), managed by the Joint Research Centre, the European Commission’s in-house science service. Disclaimer The scientific output expressed does not imply a policy position of the European Commission. Neither the European Commission nor any person acting on behalf of the Commission is responsible for the use which might be made of this publication. Copyright notice © European Union, 2014. Reuse is authorised, provided the source is acknowledged. The reuse policy of the European Commission is implemented by the Decision on the reuse of Commission documents of 12 December 2011. Bibliographic Information: Ann Crabbé, Danny Vandenbroucke, Andreas Matheus, Dirk Frigne, Frank Maes and Reijer Copier Authenti- cation, Authorization and Accounting for Data and Services in EU Public Administrations: D1.1.2 & D1.2.2 – Analysing standards and technologies for AAA. European Commission; 2014. JRC92555 1 ARe3NA Crabbé et al. (2014) AAA for Data and Services (D1.1.2 & D1.2.2): Analysing Standards &Technologies for AAA Contents 1.
    [Show full text]
  • Knihovna Pro Prístup K Federacím Identit
    MASARYKOVA UNIVERZITA F}w¡¢£¤¥¦§¨ AKULTA INFORMATIKY !"#$%&'()+,-./012345<yA| Knihovna pro pˇrístup k federacím identit BAKALÁRSKÁˇ PRÁCE Marcel Poul Brno, 2011 Prohlášení Prohlašuji, že tato bakaláˇrskápráce je mým p ˚uvodnímautorským dílem, které jsem vypracoval samostatnˇe.Všechny zdroje, prameny a literaturu, které jsem pˇrivypracování používal nebo z nich ˇcerpal,v práci ˇrádnˇecituji s uvedením úplného odkazu na pˇríslušnýzdroj. Marcel Poul Vedoucí práce: RNDr. Daniel Kouˇril iii Podˇekování Tímto dˇekujivedoucímu mé bakaláˇrsképráce RNDr. Danielu Kouˇriloviza cenné rady a ˇcas,který mi vˇenovalpˇriˇrešenídané problematiky. v Shrnutí Tato práce se vˇenujenávrhu knihovny pro pˇrístupk federacím identit a její implementaci pomocí jakyka C. V práci je pˇredstavenprincip federací iden- tit a popsán návrh a implementace knihovny. vii Klíˇcováslova Federace identit, poskytovatel služeb, poskytovatel identit, SAML, Shibbo- leth ix Obsah 1 Úvod ................................... 3 2 Federace identit ............................. 5 2.1 Struktura federací ......................... 5 2.2 Security Assertion Markup Language (SAML) . 7 2.3 Shibboleth ............................. 7 2.4 Federace eduID.cz ......................... 8 2.5 SWITCHaai ............................ 9 2.6 eduroam .............................. 9 2.7 OpenID ............................... 10 2.8 MojeID ............................... 11 3 Návrh knihovny pro pˇrístupk federacím identit . 13 3.1 Analýza proces ˚upˇripˇrístupuk federacím identit . 13 3.2 Požadavky na ˇrešení
    [Show full text]
  • Eidas-Node and SAML
    eIDAS-Node and SAML Version 1.0 eIDAS-Node and SAML Version 1.0 Document history Version Date Modification reason Modified by 1.0 06/10/2017 Origination DIGIT Disclaimer This document is for informational purposes only and the Commission cannot be held responsible for any use which may be made of the information contained therein. References to legal acts or documentation of the European Union (EU) cannot be perceived as amending legislation in force or other EU documentation. The document contains a brief overview of technical nature and is not supplementing or amending terms and conditions of any procurement procedure; therefore, no compensation claim can be based on the contents of the present document. Copyright European Commission — DIGIT Page 2 of 59 eIDAS-Node and SAML Version 1.0 Table of contents DOCUMENT HISTORY ...................................................................................... 2 TABLE OF CONTENTS ...................................................................................... 3 LIST OF FIGURES ........................................................................................... 5 LIST OF TABLES ............................................................................................. 6 1. INTRODUCTION ....................................................................................... 7 1.1. Document aims ............................................................................... 7 1.2. Document structure ......................................................................... 7 1.3.
    [Show full text]
  • Implementation Experiences on IHE XUA and BPPC1 December 5, 2006
    Implementation Experiences On IHE XUA and BPPC1 December 5, 2006 Tuncay Namlı and Asuman Dogac Software Research and Development Center Middle East Technical University Ankara, Turkey The most up-to-date version of this document is available from http://www.srdc.metu.edu.tr/publications 1 This work is supported in part by the European Commission, eHealth Unit (http://ec.europa.eu/information_society/activities/health/index_en.htm) through the 027074 Saphire Project (http://www.srdc.metu.edu.tr/webpage/projects/saphire/) and by the Scientific and Technical Research Council of Turkey (TUBITAK) through the Project No. EEEAG 105E133. LIST OF FIGURES.......................................................................................................................................2 LIST OF ACRONYMS.................................................................................................................................3 1 OVERVIEW.........................................................................................................................................3 2 EXECUTIVE SUMMARY .................................................................................................................4 3 THE IMPLEMENTATION SCENARIO..........................................................................................5 4 TRUST MODEL..................................................................................................................................7 4.1 TRUST MODEL IN AN AFFINITY DOMAIN.......................................................................................7
    [Show full text]
  • Ebxml Registry Services and Protocols Version
    1 2 ebXML Registry Services and Protocols 3 Version 3.0 4 Committee Draft Specification 02, 15 March, 2005 5 Document identifier: 6 regrep-rs-3.0-cd-02 7 Location: 8 http://www.oasis-open.org/committees/regrep/documents/3.0/specs/regrep-rs-3.0-cd-02.pdf 9 Editors: Name Affiliation Sally Fuger Individual Farrukh Najmi Sun Microsystems Nikola Stojanovic RosettaNet 10 11 Contributors: Name Affiliation Diego Ballve Individual Ivan Bedini France Telecom Kathryn Breininger The Boeing Company Joseph Chiusano Booz Allen Hamilton Peter Kacandes Adobe Systems Paul Macias LMI Government Consulting Carl Mattocks CHECKMi Matthew MacKenzie Adobe Systems Monica Martin Sun Microsystems Richard Martell Galdos Systems Inc Duane Nickull Adobe Systems Goran Zugic ebXMLsoft Inc. 12 13 Abstract: 14 This document defines the services and protocols for an ebXML Registry 15 A separate document, ebXML Registry: Information Model [ebRIM], defines the types of metadata 16 and content that can be stored in an ebXML Registry. 17 Status: 18 This document is an OASIS ebXML Registry Technical Committee Approved Draft Specification. 19 Committee members should send comments on this specification to the [email protected] 20 open.org list. Others should subscribe to and send comments to the [email protected] 21 open.org list. To subscribe, send an email message to [email protected] 22 open.org with the word "subscribe" as the body of the message. 23 For information on whether any patents have been disclosed that may be essential to 24 implementing this specification, and any offers of patent licensing terms, please refer to the 25 Intellectual Property Rights section of the OASIS ebXML Registry TC web page (http://www.oasis- 26 open.org/committees/regrep/).
    [Show full text]
  • SAML Implementation Guidelines
    1 2 3 SAML Implementation Guidelines 4 Working Draft 01, 27 August 2004 5 Document identifier: 6 sstc-saml-implementation-guidelines-draft-01 7 Location: 8 http://www.oasis-open.org 9 Editor: 10 Charles Knouse ([email protected]) 11 Contributors: 12 Liberty ID-FF Implementation Guideline contributors 13 Abstract: 14 This non-normative specification provides guidelines for the implementation of applications using 15 SAML assertions, protocol, bindings, and profiles. 16 Status: 17 This is a working draft produced by the Security Services Technical Committee. Publication of this 18 draft does not imply TC endorsement. This is an active working draft that may be updated, 19 replaced or obsoleted at any time. See the revision history for details of changes made in this 20 revision. 21 Committee members should submit comments and potential errata to the security- 22 [email protected] list. Others should submit them to the security-services- 23 [email protected] list (to post, you must subscribe; to subscribe, send a message to 24 [email protected] with "subscribe" in the body) or use 25 other OASIS-supported means of submitting comments. The committee will publish vetted errata 26 on the Security Services TC web page (http://www.oasis-open.org/committees/security/). 27 For information on whether any patents have been disclosed that may be essential to 28 implementing this specification, and any offers of patent licensing terms, please refer to the 29 Intellectual Property Rights web page for the Security Services TC (http://www.oasis- 30 open.org/committees/security/ipr.php).
    [Show full text]
  • SAML 2.0 Profile of XACML 2.0 V2
    2 SAML 2.0 Profile of XACML, 3 Version 2.0 4 Committee Specification 01 5 10 August 2010 6 Specification URIs: 7 This Version: 8 http://docs.oasis-open.org/xacml/3.0/xacml-profile-saml2.0-v2-spec-cs-01-en.html 9 http://docs.oasis-open.org/xacml/3.0/xacml-profile-saml2.0-v2-spec-cs-01-en.odt (Authoritative) 10 http://docs.oasis-open.org/xacml/3.0/xacml-profile-saml2.0-v2-spec-cs-01-en.pdf 11 Previous Version: 12 http://docs.oasis-open.org/xacml/3.0/xacml-profile-saml2.0-v2-spec-cd-03-en.html 13 http://docs.oasis-open.org/xacml/3.0/xacml-profile-saml2.0-v2-spec-cd-03-en.odt (Authoritative) 14 http://docs.oasis-open.org/xacml/3.0/xacml-profile-saml2.0-v2-spec-cd-03-en.pdf 15 Latest Version: 16 http://docs.oasis-open.org/xacml/3.0/xacml-profile-saml2.0-v2-spec-en.html 17 http://docs.oasis-open.org/xacml/3.0/xacml-profile-saml2.0-v2-spec-en.odt (Authoritative) 18 http://docs.oasis-open.org/xacml/3.0/xacml-profile-saml2.0-v2-spec-en.pdf 19 Technical Committee: 20 OASIS eXtensible Access Control Markup Language (XACML) TC 21 Chair(s): 22 Hal Lockhart <[email protected]> 23 Bill Parducci <[email protected]> 24 Editors: 25 Erik Rissanen <[email protected]> 26 Hal Lockhart <[email protected]> 27 Related Work: 28 This specification replaces and supersedes: 29 • SAML 2.0 profile of XACML 2.0 30 This specification is related to: 31 • Assertions and Protocols for the OASIS Security Assertion Markup Language(SAML)v 2.0 32 OASIS Standard xacml-profile-saml2.0-v2-spec-cs-01-en 10 Aug 2010 Copyright © OASIS® 2010.
    [Show full text]
  • Picketlink Picketlink Reference Documentation
    PicketLink PicketLink Reference Documentation PicketLink PicketLink Reference Documentation PicketLink PicketLink Reference Documentation PicketLink Author Copyright © 2014 Red Hat. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries. Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project. The OpenStack® Word Mark and OpenStack Logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation's permission.
    [Show full text]
  • Technical Data Sheet Dirx Access V8.3 Web Access Management and Identity Federation
    Technical Data Sheet DirX Access V8.3 Web Access Management and Identity Federation DirX Access is a comprehensive, cloud-ready, scalable, and highly available access management solution providing policy-based authentication, authorization and federation for Web applications and services. DirX Access delivers single sign-on, versatile authentication, SAML- and OAuth-based identity federation and proxying, just-in-time provisioning, entitlement management and policy enforcement for applications and services in the cloud or on-premise. Your business technologists. Powering progress Web Access Management and Identity Federation Everything and everyone is always online, and securing access to applications provided either Protected Authentication Authorization Federation as on- and off-premise services or from the SAML, OAuth cloud has never been more important. Systems Businesses and government agencies are Web accelerating the formation of online partner- Entitlement Servers ships to respond quickly to potential revenue User Session Management Management Management HTTP opportunities, outsource non-core functions, XACML SOAP Application and deliver the widest variety of services to Servers their users. WS-* Web Policy Web Services To improve operational efficiency and respond Single Sign-On Management Security SAML Fine-grained WS-Trust, STS Web to user demand, they continue to put more and SSO policies Services more critical data and applications online for information sharing and self-service by con- sumers, mobile employees, channel partners Audit Delegated, Integration and and Role-Based Customization Applications and suppliers. Logging Administration Framework Cloud adoption has soared as it has proved to offer great economies of scale for many organi- zations by providing a lower-cost, flexible way to use applications and services.
    [Show full text]
  • SAML Version 2.0 Scope and Work Items
    1 2 SAML Version 2.0 Scope and Work Items 3 Working Draft 178, 5 April3 May 2004 4 Document identifier: 5 sstc-saml-scope-2.0-draft-187 6 Location: 7 http://www.oasis-open.org/committees/documents.php?wg_abbrev=security 8 Previous draft: 9 http://www.oasis-open.org/committees/download.php/6113/sstc-saml-scope-2.0-draft-16-diff.pdf 10 Editors: 11 Scott Cantor, individual ([email protected]) 12 Prateek Mishra, Netegrity ([email protected]) 13 Eve Maler, Sun Microsystems ([email protected]) 14 Abstract: 15 This non-normative document describes the scope of the V2.0 work of the OASIS Security 16 Services Technical Committee (SSTC), including candidate work items and their status. 17 Status: 18 Revision 187 reflects the results of work done during April 2004the F2F meeting held 30 March to 19 1 April 2004 in Austin, TX. W-5, W-6, and W-7 were completed; W-15 was made inactive (though 20 parts of it were completed in V2.0); notes for active work item were updated; and the official 21 OASIS notice was added as an appendix. sstc-saml-scope-2.0-draft-18 3 May 2004 Copyright © OASIS Open 2004. All Rights Reserved. Page 1 of 18 20 1 Scope of the V2.0 Work 21 The SAML 2.0 effort intends to deliver on the following goals: 22 • Address issues and enhancement requests that have arisen from experience with real-world SAML 23 implementations and with other security architectures that use SAML. 24 • Adding support for features that were deferred from previous versions of SAML.
    [Show full text]
  • Identity & Authorization Management (I.AM) Federation Metadata
    Identity & Authorization Management (I.AM) Federation Metadata This document is provided to you free of charge by the eHealth platform Willebroekkaai 38 38, Quai de Willebroek 1000 BRUSSELS All are free to circulate this document with reference to the URL source. Table of contents Table of contents .................................................................................................................................................... 2 1. Document management ........................................................................................................................ 3 1.1 Document history ................................................................................................................................... 3 2. Introduction ........................................................................................................................................... 4 2.1 Goal of the document ............................................................................................................................ 4 3. EntityDescriptor ..................................................................................................................................... 5 3.1 RoleDescriptor........................................................................................................................................ 5 3.1.1 KeyDescriptor ......................................................................................................................................... 5 3.2 IDPSSODescriptor ..................................................................................................................................
    [Show full text]
  • Redalyc.Managing Dynamic Identity Federations Using Security
    Journal of Theoretical and Applied Electronic Commerce Research E-ISSN: 0718-1876 [email protected] Universidad de Talca Chile Ferdous, Md. Sadek; Poet, Ron Managing Dynamic Identity Federations using Security Assertion Markup Language Journal of Theoretical and Applied Electronic Commerce Research, vol. 10, núm. 2, mayo, 2015, pp. 53-76 Universidad de Talca Curicó, Chile Available in: http://www.redalyc.org/articulo.oa?id=96538544005 How to cite Complete issue Scientific Information System More information about this article Network of Scientific Journals from Latin America, the Caribbean, Spain and Portugal Journal's homepage in redalyc.org Non-profit academic project, developed under the open access initiative Journal of Theoretical and Applied Electronic Commerce Research This paper is available online at ISSN 0718–1876 Electronic Version www.jtaer.com VOL 10 / ISSUE 2 / MAY 2015 / 53-76 DOI: 10.4067/S0718-18762015000200005 © 2015 Universidad de Talca - Chile Managing Dynamic Identity Federations using Security Assertion Markup Language Md. Sadek Ferdous1 and Ron Poet2 1 School of Computing Science, University of Glasgow, Glasgow, Scotland, [email protected] 2 School of Computing Science, University of Glasgow, Glasgow, Scotland, [email protected] Received 23 January 2014; received in revised form 14 September 2014; accepted 22 September 2014 Abstract Security Assertion Markup Language is one of the most widely used technologies to enable Identity Federations among different organisations. Despite its several advantages, one of its key disadvantages is that it does not allow creating a federation in a dynamic fashion to enable service provisioning (or de-provisioning) in real time.
    [Show full text]