Service Oriented Architecture for Distributed Identity Management System

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    1 Favorite

    Service Oriented Architecture for Distributed Identity Management System - Presentation Transcript

    1. Service Oriented Architecture for Distributed Identity Management System Adam Gzella
    2. Outline
      • Scenario
      • SOA as a solution
      • REST vs. SOAP
      • Final system architecture
      • System perspectives
    3. Take-away message (motto)
      • Main goal is to help people with multiple credentials problem and complicated registration process.
      • Achieved by simple, universal identity management system:
        • D-FOAF extended with SOA.
    4. Scenario
      • Alice registered to the travel.com easily (possibly with FOAF profile)
      • then she logs to the service and manage the profile
      travel.com FOAFRealm FOAF login(); Alice
    5. Scenario
      • Alice logs into music.com and games.com without new registration
      travel.com FOAFRealm music.com FOAFRealm games.com FOAFRealm D-FOAF Alice
    6. Scenario
      • Alice uses lot more various services (build with varius languages) with the same credentials.
      • How to achieve this?
      • How to make D-FOAF popular - solve multiple credentials problem?
      • Separate implementations or unified service access method?
      Mobiles Java PHP .Net D-FOAF ?
    7. Scenario
      • Alice uses lot more various services with the same credentials.
      travel.com FOAFRealm music.com FOAFRealm games.com FOAFRealm D-FOAF movies.com fun.com sport.com pets.com SOA (REST) SOA (REST) SOA (REST) Alice
    8. Why SOA?
      • Fully Web oriented
        • FOAFRealm/D-FOAF is Web appliaction
      • Language independent
      • Platform independent
      SOA Linux C/C++ JME Windows JEE .Net PHP
    9. SOA Implementation – REST vs SOAP
      • Why REST was selected?
        • Resource oriented.
        • Semantic Web compilant (URI, RDF)
        • Real Web utilisation (HTTP)
        • Simplicity and clearness
      ?
    10. REST SOA - Example FOAFRealm SOA (REST) GET http://foafrealm.org/soa/alice@exmpl.org/nick POST http://foafrealm.org/soa/alice@exmpl.org/nick (with authentication information) Alice RDF RDF(with new nick)
    11. Final system
      • Universal Identity Management System
        • JEE, PHP, .Net, JME implementations
        • Backward compatibility
      • In wider scope:
        • solution for multiple credentials problem.
    12. Final system – perspectives
      • Lot of possible future implementations:
        • next version of JeromeDL (semantic digital librar ies )
        • DigiMe
        • MarcOnt Portal
        • Didaskon
      • Extending SOA to other FOAFRealm modules, like SSCF (Social Semantic Collaborative Filtering)
      • Adam Gzella
      • [email_address]
      • National University of Ireland, Galway
      • Digital Enterprise Research Institute

    + adameqadameq, 3 years ago

    custom

    4838 views, 1 favs, 0 embeds more stats

    Short presentation of SOA leyer for FOAFRealm (Dist more

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 4838
      • 4838 on SlideShare
      • 0 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 190
    Most viewed embeds

    more

    All embeds

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories