NOTE: 2016-06-23
52°North is migrating this TWiki to foswiki which will become availabe via the well known domain wiki.52north.org soon.
Hence, this wiki is switched to read-only mode starting Monday - 27.06.2016 - until the end of the migration. Hence, save your changes beforehand.

The 52°North IT-Team.

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 Contributor/ConceptualWork

Licensing Workflow

A brief presentation for the licensing workflow in 52n (in German)

Topic attachments
I Attachment Action Size Date Who Comment
PDFpdf Licensing_in_52n.pdf manage 111.8 K 2009-10-21 - 12:50 ThorstenDeelmann Licensing scenarios in 52n (in German)
Tags:
create new tag
, view all tags
Topic revision: r16 - 2014-10-15 - 14:00:55 - EikeHinderkJuerrens

 
  • Search: 
This site is powered by the TWiki collaboration platform Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback