© ETNIC l l Anne Noseda l WSGenCon 2.0 Presentation 1 WSGenCon /02/2010 E2SA – Equipe Support Standard Architecture
© ETNIC l l WSGenCon 2.0 Presentation 2 Goals ETNIC developed a gateway called WSGenCon Why ? How ? Table of Contents 1.Context 2.Problems encountered 3.WSGenCon Future 5.Demo l Goals & Contents Goals & Contents
© ETNIC l l WSGenCon 2.0 Presentation 3 1. Context l Education Web Services ETNIC provides education Web Services (WS) Exposed on the Internet Need to be secured ETNIC has to know who registers Signature Non-repudiation ETNIC’s choices : Use of standards WS-Security + certificate (WSS X.509 Certificate Token Profile) user Registration WS Registration Application School Internet
© ETNIC l l WSGenCon 2.0 Presentation 4 Part of Novell IAM Solution Goal : Securing WS Supports a lot of standards Graphical interface – easy to configure 1. Context l ETNIC - Layer 7
© ETNIC l l WSGenCon 2.0 Presentation 5 2. Problems encountered l Technical complexity WS-Security too complex for schools ETNIC developed a gateway : WSGenCon WSGenCon 1.0 provides XML support (XSL) SOAP protocol support WS-* support (WS-Adressing, WS-Security + certificate signature) HTTP / HTTPS protocol support
© ETNIC l l WSGenCon 2.0 Presentation 6 2. Problems encountered l Certificate vs eID WSGenCon 1.0 offers 2 ways of signing : Simple certificate Belgium electronic identity card (eID) eID clearly better Comparison pointscertificateeID Cost--+ Diffusion--++ Lifecycle management-+ Technical complexity+- Secured storage--++
© ETNIC l l WSGenCon 2.0 Presentation 7 2. Problems encountered l Problems with WSGenCon 1.0 Organizational problems PO provides same certificate to each school > cost Technical problems use of eID : at each registration, PIN code requested Solution WSGenCon 2.0 with WS-SecureConversation
© ETNIC l l WSGenCon 2.0 Presentation 8 3. WSGenCon 2.0 l WS-SecureConversation 2 OASIS Standards : WS-Trust (WST) WS-SecureConversation (WSSC) User authenticated once by STS One PIN code request Then, use of a Security Context Token (SCT) no more PIN code request
© ETNIC l l WSGenCon 2.0 Presentation 9 3. WSGenCon 2.0 l Technical issues Layer 7 constraints : Security Token Service (STS) + Secure Span Gateway (SSG) = same product SCT is known by both elements WSSC specification advices to use derived key instead of the SCT itself Mandatory If RST is signed, RSTR is also signed Decryption not allowed with eID Layer 7 support team proposed use of SSL mutual authentication
© ETNIC l l WSGenCon 2.0 Presentation WSGenCon 2.0 l Mutual SSL
© ETNIC l l WSGenCon 2.0 Presentation WSGenCon 2.0 l WSGenCon 2.0
© ETNIC l l WSGenCon 2.0 Presentation Future l What’s more to do ? Nearly ready to use Update our Forge Website (source code & documentation) Package WSGenCon 2.0 simple installer Test for Java 1.5 (only compatible Java 6) Create user documentation
© ETNIC l l WSGenCon 2.0 Presentation Demo l Demonstration FASE WS school details Use of test eID provided by Certipost First launch : WS-Trust token negotiation 2 XML messages in the console WS-SecureConversation business exchanges 2 XML messages Second launch : Token is present and not expired Only WS-SecureConversation business exchanges 2 XML messages
© ETNIC l l WSGenCon 2.0 Presentation 14 Questions l Questions E2SA contact information : Equipe Support Standard Architecture Anne Noseda – 02/ Sébastien Bal – 02/ E2SA responsible for : WSGenCon support / development Layer 7 policies development WS development on the ESB
© ETNIC l l WSGenCon 2.0 Presentation 15 Conclusion l Conclusion This practical use case has proven that : it is possible to use only standards eID can be integrated with standards Information & source code will be available at Feel free to usehttp://forge.etnic.be
© ETNIC l l WSGenCon 2.0 Presentation 16