Service Oriented Architecture for Distributed Identity Management System

5,001 views

Published on

Short presentation of SOA leyer for FOAFRealm (Distributed Identity Management System). It shows the motivation and how the goals were achieved.

Published in: Education, Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
5,001
On SlideShare
0
From Embeds
0
Number of Embeds
45
Actions
Shares
0
Downloads
237
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Service Oriented Architecture for Distributed Identity Management System

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

×