DOCSLIB.ORG

Sociotal Creating a Socially Aware Citizen-Centric Internet of Things

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Sociotal Creating a Socially Aware Citizen-Centric Internet of Things Ref. Ares(2017)3187879 - 26/06/2017 Specific Targeted Research Projects (STReP) SocIoTal Creating a socially aware citizen-centric Internet of Things FP7 Contract Number: 609112 WP1 – Socially-aware citizen centric architecture and community APIs Deliverable report Contractual date of delivery:31/08/2016 Actual submission date: 31/08/2016 Deliverable ID: D1.2.2 Deliverable Title: Final version of SocIoTal Architecture Responsible beneficiary: UNIS Contributing beneficiaries: UNIS, CEA, UC, CRS4, DNET, UMU Start Date of the Project: 1 September 2013 Duration: 36 Months Revision: 1 Dissemination Level: Public PROPRIETARY RIGHTS STATEMENT This document contains information, which is proprietary to the SOCIOTAL Consortium. Neither this document nor the information contained herein shall be used, duplicated or communicated by any means to any third party, in whole or in parts, except with prior written consent of the SOCIOTAL consortium. FP7 Contract Number: 609112 Deliverable report – WP1 / T1.2/D1.2.1 Document ID: D1.2.1 Document Information Document ID: D1.2.2 Version: Final 1.0 Version Date: 31 August 2016 Authors: Colin O’Reilly (UNIS), Ignacio Elicegui (UC), Carmen Lopez (UC), Luis Sanchez (UC), Jose Luis Hernández, Jorge Bernabé (UMU), Alberto Serra (CRS4), Nenad Gligoric, Srdjan Krco (DNET), Christine Hennebert (CEA), Alexandre MACABIES (CEA), Niklas Palaghias (UNIS) Security: Public Approvals Name Organization Date Visa Project Management K. MOESSNER UNIS Team Internal Reviewer Colin O’Reilly UNIS 24/08/2016 Internal Reviewer Srdjan Krco DNET 24/08/2016 Document history Revision Date Modification Authors Draft 23/5/2016 First Draft ToC CEA V0 Preliminar version CEA V1 05/07/2016 First version – to be completed by partners CEA V2 03/08/2016 Second version – Merge of the contributions CEA V3 12/08/2016 Third version – New merge of contributions CEA V4 22/08/2016 Need to add references CEA Internal 23/08/2016 Ready for internal review CEA review FINAL 01/09/2016 Finale Version CEA Version Date: 25 November 2016 Security: Confidential Page II FP7 Contract Number: 609112 Deliverable report – WP1 / T1.2/D1.2.1 Document ID: D1.2.1 Content Section 1 - Beyond IoT-A methodology ........................................................................... 6 1.1 IoT-A Architecture Reference Model (ARM) ......................................................... 6 1.2 Architecture of the SocIoTal platform .................................................................. 7 Section 2 - Beyond Fi-Ware: the SocIoTal platform........................................................ 9 2.1 Components and Enablers description ................................................................ 9 2.2 Enhancement of FIWARE platform ..................................................................... 23 Section 3 - Final Data Models ......................................................................................... 30 3.1 Context Manager .................................................................................................. 30 3.2 Security Server AAA ............................................................................................ 30 3.3 Trust Manager ....................................................................................................... 34 3.4 Profile Manager ..................................................................................................... 37 3.5 Interaction of Sensinact with the platform ......................................................... 39 3.6 Enablers ................................................................................................................ 44 3.7 User environment ................................................................................................. 50 Section 4 - Deployment of SocIoTal platform ............................................................... 54 4.1 Context Manager .................................................................................................. 54 4.2 Security Server AAA ............................................................................................ 57 4.3 Identity Manager ................................................................................................... 59 4.4 Trust Manager ....................................................................................................... 60 4.5 Profile Manager ..................................................................................................... 62 4.6 Authorized access to data from sensiNact studio ............................................ 66 4.7 Enablers ................................................................................................................ 68 Section 5 - Horizontal testbeds ...................................................................................... 71 5.1 Description of the Scenario ................................................................................. 71 5.2 Scheduling of the process ................................................................................... 71 5.3 Deployment of the scenario from SocIoTal github ............................................ 72 Section 6 - Success indicators ....................................................................................... 78 6.1 Innovation, development of new components and enablers ........................... 78 6.2 Security & Privacy by design .............................................................................. 80 Section 7 - Conclusion .................................................................................................... 82 References ............................................................................................................................ 83 Abbreviations and Acronyms ............................................................................................. 84 Version Date: 25 November 2016 Security: Confidential Page III FP7 Contract Number: 609112 Deliverable report – WP1 / T1.2/D1.2.1 Document ID: D1.2.1 Table of the figures Figure 1: Translating Perspective to View ................................................................................ 6 Figure 2: architecture of the SocIoTal platform ........................................................................ 8 Figure 3: Graphical Interface of sensinact studio ..................................................................... 9 Figure 4: user location (red marker) computed from static nodes (blue dots) ........................ 13 Figure 5 Trust Manager integration with the Context Manager .............................................. 15 Figure 6 : Group Manager Instantiation and integration with the Context Manager ............... 16 Figure 7: SocIoTal authorization scenario .............................................................................. 21 Figure 8: interactions between sensiNact studio and sensiNact gateway .............................. 24 Figure 9: Application deployment. .......................................................................................... 25 Figure 10: Stream Processing Principle ................................................................................. 26 Figure 11: Communication between Esper engine and the gateway components ................ 27 Figure 12: Application component .......................................................................................... 28 Figure 13: Application lifecycle ............................................................................................... 28 Figure 14 : Application watchdog ........................................................................................... 29 Figure 15: SocIoTal Context Data according OMA and IoT-A ............................................... 30 Figure 16: Capability Token example ..................................................................................... 32 Figure 17: Update message example for CP-ABE based group communication ................... 39 Figure 18: Subscription message example for CP-ABE based group communication .......... 39 Figure 19: Gait recognition modules ...................................................................................... 47 Figure 20: User Environment Data model .............................................................................. 51 Figure 21: SocIoTal Centralized Context Manager framework .............................................. 54 Figure 22: Current SocIoTal Context Manager implementation ............................................. 56 Figure 23: Current SocIoTal Communities Manager implementation .................................... 63 Figure 24: Integration of sensiNact into the SocIoTal platform .............................................. 66 Figure 25: Secured access sequence diagram ...................................................................... 67 Figure 26: Access right inheritance diagram example ........................................................... 68 Figure 27 : the radio location process .................................................................................... 69 Figure 28: in the field pictures of the experiment ................................................................... 70 Figure 29: scheduling of the scenario .................................................................................... 72 Version Date: 25 November 2016 Security: Confidential Page IV FP7 Contract Number: 609112 Deliverable report – WP1 / T1.2/D1.2.1 Document ID: D1.2.1 Executive
Load more

Recommended publications
  • Realization of the System for Access Management and Identity Federation with Use of Service Mojeid and the Product Dirx Access
    MASARYKOVA UNIVERZITA FAKULTA}w¡¢£¤¥¦§¨ INFORMATIKY !"#$%&'()+,-./012345<yA| Realization of the system for access management and identity federation with use of service mojeID and the product DirX Access. DIPLOMA THESIS Jakub Šebök Brno, Autumn 2014 Declaration Hereby I declare, that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Jakub Šebök Advisor: RNDr. JUDr. Vladimír Šmíd, CSc. ii Acknowledgement I would like to thank firstly to my technical consultant Filip Höfer for his guidance. Secondly I thank to Mr. Šmíd for his advice about methodology and formal formatting of the thesis. And lastly I would like to thank all who survived by my side and cheered me up espe- cially during last months before the deadline. These are namely my mom, my girlfriend, Anton Gierlti, Matej Chrenko, Buddha and Bill Cosby. Thank you all again for enormous support. iii Abstract The aim of this thesis is implementation of a client program on the side of DirX Access which cooperates with the Czech identity provider mojeID. This cooperation consists of authenticating users by third party authority such that their credentials can be used for further processing in access management mechanism of DirX Access. iv Keywords security, SSO, OpenID, policies, RBAC, identity, mojeID, access man- agement, authentication, authorization v Contents 1 Introduction ............................3 2 Internet Security and Terminology ..............5 2.1 Identity ............................5 2.2 Identity Provider and Relying Party ...........6 2.3 Claims vs.
    [Show full text]
  • Trusted Computing Or Distributed Trust Management?
    Trusted computing or distributed trust management? Michele Tomaiuolo Dipartimento di Ingegneria dell’Informazione Università di Parma Via Usberti, 181/A – 43100 Parma – Italy [email protected] Abstract Nowadays, in contrast with centralized or hierarchical certification authorities and directory of names, other solutions are gaining momentum. Federation of already deployed security systems is considered the key to build global security infrastructures. In this field, trust management systems can play an important role, being based on a totally distributed architecture. The idea of distributed trust management can be confronted with the concept of trusted computing. Though having a confusingly similar denomination, the different interpretation of trust in these systems drives to divergent consequences with respect to system architectures and access policies, but also to law, ethics, politics. While trusted computing systems assure copyright holders and media producers that the hosting system will respect the access restrictions they defined, trust management systems, instead, allow users to grant trust to other users or software agents for accessing local resources. Keywords Data security, Security Management, Authentication, Authorization, Intellectual Property Rights, Information Access, Digital Books, Multimedia, Web Technologies Introduction A number of architectures and systems are being proposed as a ground for improved interoperability among diverse systems, mainly exploiting the idea of service-oriented architecture. Yet, some issues remain open. In fact, composition of services requires some delegation of goals and duties among partners. But these delegations cannot come into effect, if they’re not associated with a corresponding delegation of privileges, needed to access some resources and complete delegated tasks, or achieve desired goals.
    [Show full text]
  • OASIS Response to NSTC Request for Feedback on Standard Practices
    OASIS RESPONSE TO NSTC REQUEST FOR FEEDBACK ON STANDARDS PRACTICES OASIS (Organization for the Advancement of Structured Information Standards) is pleased to respond to the request from the National Science and Technology Council's Sub-Committee on Standards published at 75 FR 76397 (2010), and extended by 76 FR 3877 (2011), for feedback and observations regarding the effectiveness of Federal agencies' participation in the development and implementation of standards and conformity assessment activities and programs. We have advised our own members about the Federal Register inquiry, in case they wish to respond. Of course, their opinions are their own, and this response does not represent the views of any members, but only the observations of OASIS professional staff. I. RESPONDENT'S BACKGROUND OASIS is one of the largest and oldest global open data standards consortia, founded in 1993 as SGML Open. OASIS has over 5000 active participants representing about 600 member organizations and individual members in over 80 countries. We host widely-used standards in multiple fields including • cybersecurity & access control (such as WS-Security, SAML, XACML, KMIP, DSS & XSPA) [/1], • office documents and smart semantic documents (such as OpenDocument, DITA, DocBook & CMIS) [/2], and • electronic commerce (including SOA and web services, such as BPEL, ebXML, WS-ReliableMessaging & the WS-Transaction standards) [/3] among other areas. Various specific vertical industries also fulfill their open standards requirements by initiating OASIS projects, resulting in mission-specific standards such as • UBL and Business Document Exchange (for e-procurement) [/4], • CAP and EDML (for emergency first-responder notifications) [/5], and • LegalXML (for electronic court filing data)[/6].
    [Show full text]
  • First Experiences Using XACML for Access Control in Distributed Systems
    First Experiences Using XACML for Access Control in Distributed Systems M. Lorch', S. Procto9, R. Lepro3, D. Kafura', S. Shah' ' Department of Computer Science, Virginia Tech Sun Microsystems Laboratories NASA Ames Research Center Abstract Authorization systems today are increasingly complex. They span domains of administration, rely on many different authentication sources, and manage permissions that can be as complex as the system itself. Worse still, while there are many standards that define authentication mechanisms, the standards that address authorization are less well defined and tend to work only within homogeneous systems. This paper presents XACML, a standard access control language, as one component of a distributed and inter-operable authorization framework. Several emerging systems which incorporate XACML are discussed. These discussions illustrate how authorization can be deployed in distributed, decentralized systems. Finally, some new and future topics are presented to show where this work is heading and how it will help connect the general components of an authorization system. 1. Introduction In modem systems, security is a critical feature. Beyond providing strong protection, security systems must also be flexible and promote inter-operability between domains of trust. However, flexibility can come at the price of simplicity and manageability, especially in the complex realm of authorization. Thus, the authorization components of a secure system must be able to work together across domains, but must be manageable to maintain their collaborative value. Authorization determines whether or not a given action, for example reading a file or logging into a server, is allowed. This is typically, though not always, achieved by authenticating a user and then using their locally assigned attributes or rights to make access decisions according to locally defined policies.
    [Show full text]
  • Emergency Management Standards
    Emergency Management Standards HL7 WGM International Council May 2019 Elysa Jones, Chair OASIS Emergency Management Technical Committee Emergency Interoperability Member Section [email protected] Agenda ▪ What is OASIS ▪ Joint work with HL7 - Tracking emergency patients - Hospital availability 2 Internationally recognized ▪ EU classifies OASIS as “one of the top three ICT consortia”. ▪ EU Regulation 1025/2012 allows OASIS specs to be referenced in public procurement ▪ OASIS is permanent member of EC’s European Multi-Stakeholder Platform on ICT Standardization ▪ OASIS TC Process is ANSI-accredited. 3 Established presence, Current agenda ▪ Nonprofit consortium ▪ Founded 1993 ▪ Global 5,000+ participants 600+ orgs & individuals in 100+ countries ▪ Home of 70+ Technical Committees ▪ Broad portfolio of standards: security, privacy, Cloud, M2M, IoT, content technologies, energy, eGov, legal, emergency management, finance, Big Data, healthcare, + other areas identified by members 4 OASIS → de jure OASIS Standard Also Approved As: Advanced Message Queuing Protocol (AMQP) ISO/IEC 19464 ebXML Collaborative Partner Profile Agreement ISO 15000-1 ebXML Messaging Service Specification ISO 15000-2 ebXML Registry Information Model ISO 15000-3 ebXML Registry Services Specification ISO 15000-4 Security Assertion Markup Language (SAML) ITU-T Rec. X.1141 Extensible Access Control Markup Language (XACML) ITU-T Rec. X.1142 OpenDocument Format (ODF) ISO/IEC 26300 Common Alerting Protocol (CAP) ITU-T Rec. X.1303 Computer Graphics Metafile (WebCGM) W3C WebCGM
    [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]
  • Tues 330 Track 3 Anoop
    A Guideline to Secure Web Services Anoop Singhal Computer Security Division NIST [email protected] Outline Web Services and their Relation to Security Dimensions for Secure Web Services Web Services Security Standards Secure Implementation Tools and Techniques Challenges and Conclusions What are Web Services? Today, we normally use Web browsers to talk to Web sites Browser names document via URL (lots of fun and games can happen here) Request and reply encoded in HTML, using HTTP to issue request to the site Web Services generalize this model so that Applications can talk to Applications Web service definition “A Web Service is a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in WSDL. Other systems interact with the Web service in a manner prescribed by its description using SOAP messages and XML.” Source: http://www.w3.org/TR/ws-arch/ Web Services Example 2 Credit SOAP response Service Loan 1 SOAP request Service 4 SOAP response 3 Rate SOAP request Service Web Services Example Rate 1 Service UDDI Registry WSDL 3 2 UDDI response UDDI inquiry Loan Service Web Service Example 1 Request Web Portal HTML page User 4 3 2 SOAP response SOAP request Loan Service Advantages of web services?* Web services provide interoperability between various software applications running on various platforms. “vendor, platform, and language agnostic” Web services leverage open standards and protocols. Protocols and data formats are text based where possible Easy for developers to understand what is going on. By piggybacking on HTTP, web services can work through many common firewall security measures without requiring changes to their filtering rules.
    [Show full text]
  • OASIS Digital Signature Services Profiles
    Tasks: Oasis-DSSP (name to be decided) http://www.oasis-open.org/committees/process.php#2.2 Preliminary Charter (1)(a) The name of the TC OASIS Digital Signature Services Profiles (1)(b) A statement of purpose, including a definition of the problem to be solved. This Technical Committee has its mandate as production of new profiles of the existing OASIS-DSS core protocol "Digital Signature Service Core Protocols, Elements, and Bindings" and maintenance of this specification and its existing profiles. If at a later date it becomes clear that a new version of DSS is necessary then this may be produced by the TC. This further includes promotion of the standard and the creation of material helping dissemination. In general terms, the TC has the goal to facilitate the processing of digital signatures and time stamps in a client server environment. (1)(c) Scope of the work The scope of activity for this TC will be within the following topics: • Support of the server-based creation and verification of different types of signatures, among which the most relevant ones are XML Sig and CMS, and timestamps, both RC 3161 and the XML time-stamps defined by OASIS DSS TC. • Maintenance of the existing OASIS-DSS standard's and core protocol "Digital Signature Service Core Protocols, Elements, and Bindings" and related profiles produced by the OASIS Digital Signature Services Technical Committee. • Production of new profiles suitable for a number of environments and purposes, which spread the usage of the specifications. • Production of an analysis of inter-relationship among existing profiles in a matrix where new profiles shall state their relationship to existing ones.
    [Show full text]
  • Secure Ebxml Business Transaction Models Applying Web Service Security Standards
    International Journal of Security and Its Applications Vol. 6, No. 2, April, 2012 Secure ebXML Business Transaction Models Applying Web Service Security Standards Dongkyoo Shin and Dongil Shin Department of Computer Engineering, Sejong University 98 Gunja-Dong, Gwangjin-Gu, Seoul 143-747, Korea {shindk, dshin}@sejong.ac.kr Abstract ebXML is an e-business standard which enables enterprises to exchange business messages, conduct trading relationships, communicate data in common terms and define and register business processes using Web services. ebXML business transaction models are proposed which allow trading partners to securely exchange business transactions by employing Web service security standard technologies. It is shown how each Web service security technology meets the ebXML standard by constructing the experimentation software and validating messages between the trading partners. Keywords: electronic commerce, ebXML, Web service security, secure business transaction 1. Introduction ebXML (Electronic Business using eXtensible Markup Language) is a suite of standards providing tools for negotiating business processes and contracts using Web services, developed by OASIS (Organization for the Advancement of Structured Information Standards) and UN/CEFACT (United Nations' Center for Trade Facilitation and E-business) [1, 2, 3]. A list of key risks for ebXML is identified as unauthorized transactions and fraud, loss of confidentiality, error detection (application, network/transport, platform), potential loss of management and audit, and potential legal liability [2]. Because ebXML relies on Web service and some of the same underlying HTTP and Web-based architecture as common Web applications, it is susceptible to similar threats and vulnerabilities. Web Service security is based on several important concepts including identification, authentication, authorization, integrity, non-repudiation, confidentiality and privacy [4].
    [Show full text]
  • Ebxml Registry Information Model Version
    1 2 ebXML Registry Information Model 3 Version 3.0 4 OASIS Standard, 2 May, 2005 5 Document identifier: 6 regrep-rim-3.0-os 7 Location: 8 http://docs.oasis-open.org/regrep-rim/v3.0/ 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 regrep-rim-3.0-os May 2, 2005 Copyright © OASIS Open 2005. All Rights Reserved. Page 1 of 78 12 13 Abstract: 14 This document defines the types of metadata and content that can be stored in an ebXML 15 Registry. 16 A separate document, ebXML Registry: Service and Protocols [ebRS], defines the services and 17 protocols for an ebXML Registry. 18 19 Status: 20 This document is an OASIS ebXML Registry Technical Committee Approved Draft 21 Specification. 22 Committee members should send comments on this specification to the [email protected] 23 open.org list. Others should subscribe to and send comments to the regrep- 24 [email protected] list. To subscribe, send an email message to regrep-comment- 25 [email protected] with the word "subscribe" as the body of the message. 26 For information on whether any patents have been disclosed that may be essential to 27 implementing this specification, and any offers of patent licensing terms, please refer to the 28 Intellectual Property Rights section of the OASIS ebXML Registry TC web page 29 (http://www.oasis-open.org/committees/regrep/).
    [Show full text]
  • OASIS: Interoperability Opportunities and Obstacles Patrick Gannon President & C.E.O
    OASIS: Interoperability Opportunities and Obstacles Patrick Gannon President & C.E.O. OASIS Copyright OASIS, 2001 OASIS – Interop. Summit Agenda • OASIS Overview • OASIS Convergence Activities • Technical Committee Activities • ebXML Status • Global Adoption Copyright OASIS, 2001 Patrick Gannon • OASIS – C.E.O., President, Board Director • UN/ECE – Chair, Team of Specialists for Internet Enterprise Development (2000-02) • BEA Systems – Sr. VP Strategic Marketing • Netfish Technologies – VP Industry Standards • Open Buying on the Internet (OBI) – Exec. Dir. • RosettaNet – Sr. Project Leader (1998) • CommerceNet – VP Strategic Programs – XML Evangelist (1997-99) Copyright OASIS, 2001 OASIS provides a framework for XML interoperability that is critical to the future success of “ electronic business. ” OASIS puts the control of XML specifications firmly in the hands of those who will use them. Jon Bosak, Sun Microsystems “Father of XML” Organizer of the Working Group that Created XML Copyright OASIS, 2001 Overview • OASIS is a member consortium dedicated to building systems interoperability specifications • We focus on industry applications of structured information standards, such as XML, SGML, & CGM. • Members of OASIS are providers, users and specialists of standards-based technologies & include organizations, individuals & industry groups. – ~200 organizational members, ~200 individual members • International, Not-for-profit, Open, Independent • Successful through industry-wide collaboration Copyright OASIS, 2001 OASIS Value • Comprehension
    [Show full text]
  • SAML and XACML Overview
    SAML and XACML Overview Prepared by Abbie Barbir, [email protected] Nortel Canada April 25, 2006 Acknowledgements Some slides are provided by > Eve Maler, Sun Microsystems > Hal Lockhart, BEA 2 Agenda > SAML History and Overview > SAML 2.0 Features > Status in ITU-T > XACML History and Overview > XACML 2.0 Features > Status in ITU-T 3 SAML Overview and History • SAML: Security Assertion Markup Language • A framework for the exchange of security-related information between trusting parties • The key standard for federated identity systems • Supports many real-world business scenarios • Widely used today for cross-domain single sign-on • OASIS Security Services Technical Committee (SSTC) • SSTC manages SAML development 4 SAML Timeline SAML 1.0 Completed: May 2002 OASIS Standard: November 2002 Liberty 1.1 Completed: Jan 2003 SAML 1.1 Completed: May 2003 Shibboleth OpenSAML 1.0 OASIS Standard: September 2003 Completed: June 2003 Liberty ID-FF 1.2 Shibboleth OpenSAML 1.1 Completed: Oct 2003 Completed: August 2003 SAML 2.0 Completed: January 2005 OASIS Standard: March 2005 5 SAML 2.0 Specification Suite • Conformance Requirements Metadata • Required “Operational Modes” Configuration data for for SAML implementations establishing agreements between SAML entities • Assertions and Protocols • The “Core” specification Authentication Context Detailed descriptions of user • Bindings authentication mechanisms • Maps SAML messages onto common communications Security and Privacy protocols Considerations Security and privacy analysis • Profiles
    [Show full text]