80 likes | 102 Views
Explore use cases involving Relying Party, Identity Provider, and Client interactions in a network architecture. Verify user identity on Browser, Lisa's Blog and Alice's Calendar, ensuring secure identification. Dive into DIX WG Charter discussions on HomeSite, MemberSite and Agent proposals, focusing on S2S via browser and HTML form conventions.
E N D
Generalized network architecture Relying Party IdentityProvider Client
Use case: Browser Lisa’s BlogHost Verify it is Lisa Alice’s Blog Leave commentas “Lisa@blog.example.com” Authenticate and allow identification Browser
Use case: App Alice’s CalendarServer Lisa’s IdentityProvider Verify it is Lisa View calendaras “Lisa@example.com” Authenticate and allow identification CalendarApp
DIX WG Charter HomeSite SAML? MemberSite Who suggestsDIX? What interchanges? Any requirements on this side? Agent
DIX Proposal(draft-merrells-dix-00 alias dmd1) HomeSite MemberWeb site S2S viabrowser HTML Formconventions Not Specified Browser
Probable BOF Concerns • Phishing • Re-use of technologies (e.g. SAML) • Appropriateness of HTML Form use • Scope… • Usefulness…