370 likes | 492 Views
Explore the evolution of security patterns and best practices in web services with industry expert Prabath Siriwardena. This session delves into the implementation of various authentication models such as SAML2 Web SSO, OAuth, and WS-Security. Gain insights into recurring security challenges and solutions such as mutual authentication, direct authentication, and the use of security tokens. Learn how these frameworks address issues related to message level security, secure conversations, and the establishment of authenticated contexts for efficient information exchange.
E N D
Web Services SecurityPatterns, Practices&Threats Prabath Siriwardena – Software Architect, WSO2
Plan for the session Patterns Standards Implementations
1995 1997
2005 SAML2 Web SSO
Direct Authentication for Web Services Basic Authentication Mutual Authentication Transport Level 2-legged OAuth
Direct Authentication for Web Services UsernameToken Profile with WS-Security Message Level Signing – X.509 Token Profile with WS-Security
Brokered Authentication for Web Services Mutual Authentication Transport Level 2-legged OAuth
Brokered Authentication for Web Services WS-Trust / STS Resource STS WS-Federation Message Level Signing – X.509 Token Profile with WS-Security Kerberos Token Profile for WS-Security
Security Solution Patterns Message Interceptor Gateway Pattern Message Level Trusted Sub System Pattern
SOAP Security UsernameToken Profile Message Level
SOAP Security Key Identifiers X.509 Token Profile & Key Referencing Message Level Direct References
SOAP Security Symmetric Binding Vs Asymmetric Binding Message Level
SOAP Security • WS-Security secures SOAP – focuses on message level security • Focuses on a single message authentication model • Each message contains everything necessary to authenticate it self • Suitable for a coarse grained messaging in which a single message at a time from the same requestor is received Message Level WS – Secure Conversation
SOAP Security • What SSL does at the transport level in point-to-point communication, WS-SecureConversation does at the SOAP layer • Removes the need of individual SOAP message carrying authentication information. • Establishes a mutually authenticated security context in which a series of messages are exchanged. • Uses public key encryption to exchange a shared secret and then onwards uses the shared key Message Level WS – Secure Conversation
SOAP Security WS-Trust Message Level
SOAP Security Message Level Sender Vouches – Subject Confirmation
SOAP Security Holder-of-Key – Subject Confirmation Message Level
SOAP Security WS-Security Policy Message Level
prabath@wso2.com Thank You…!!!