ShibbolethImpl
Spring Integration
Application of WS-* Specifications
Licensing Workflow
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:
Gateway stellt GetMetadata-Request
GK antwortet mit
GetMetadata
-Responseund erwartet SAML-Token
GW stellt
GetMetadata
-Request an STS (Security Token Service)
STS antwortet mit
GetMetadata
-ResponseSTS stellt SAML Token gegen Vorlage eines gueltigen
UsernameToken
aus
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)
Attachments
1
Attachments
1
I
Attachment
Action
Size
Date
Who
Comment
pdf
Licensing_in_52n.pdf
manage
111 K
21 Oct 2009 - 12:50
UnknownUser
Licensing scenarios in 52n (in German)
This topic: Security
>
WebHome
>
ConceptualWork
Topic revision:
15 Oct 2014,
EikeJuerrens
Legal Notice
|
Privacy Statement
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Wiki?
Send feedback