ShibbolethImpl

Spring Integration

Application of WS-* Specifications

Increased using of WS-* Standards
  • WS-Addressing to address service endpoints
  • WS-Policy and WS-SecurityPolicy to define rules
  • WS-MetadataExchange to exchange Metadata like Policies and WSDL
  • WS-Trust to issue and convert Tokens
Using

  • Apache Axis2 as SOAP-Engine
  • Apache Rampart as WS-Security Implementation
  • Apache Neethi as WS-Policy and WS-SecurityPolicy Framework
  • Apache Rahas as WS-Trust Implementation (current: Version 1.4)
Scenario:

  1. Gateway stellt GetMetadata-Request
  2. GK antwortet mit GetMetadata-Response und erwartet SAML-Token
  3. GW stellt GetMetadata-Request an STS (Security Token Service)
  4. STS antwortet mit GetMetadata-Response STS stellt SAML Token gegen Vorlage eines gueltigen UsernameToken aus
  5. GW schickt RequestSecurityToken ueber HTTPS, STS ueberprueft angegebenes Passwort erwidert Anfrage mit RequestSecurityTokenResponse STS signiert Token
Martins ConceptualWork

Licensing Workflow

A brief presentation for the licensing workflow in 52n (in German)
Topic attachments
I Attachment Action Size Date Who Comment
Licensing_in_52n.pdfpdf Licensing_in_52n.pdf manage 111 K 21 Oct 2009 - 12:50 ThorstenDeelmann Licensing scenarios in 52n (in German)
Topic revision: r16 - 15 Oct 2014 14:00:55, EikeJuerrens - This page was cached on 22 Jul 2016 - 03:19.

This site is powered by FoswikiCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Wiki? Send feedback