OGSA Profiles Interoperability Testing
Dr. David Snelling
Fujitsu Laboratories of Europe
© 2006 Open Grid Forum
Test Scenarios
• Security
• Basic Security Profile 1.0 – core
• Security Profile 1.0 – secure channel
•
•
•
•
Approach to Security in Interop
WS-naming
WSRF Basic Profile 1.0
ByteIO/DMI/BES/JSDL
© 2006 Open Grid Forum
2
OGSA BSP - Core
Test Targets
Test Scenario
• What’s the point?
• R0301
• EPR MUST include
EndpointKeyInfo element.
• R0302
• EPR MUST include only
one EndpointKeyInfo
element.
© 2006 Open Grid Forum
3
OGSA BSP - Secure Channel
Test Targets
Test Scenario
• R0301/02
•
• Use HTTP
Requirements are on both
client and server.
• No need to have a WS.
• Client should fetch back
the fingerprint of her
own certificate.
• Root certificate
distribution out of band.
• R0303/04/05/06
•
MUST use TLS/SSL for HTTP
and non-HTTP connections.
• R0307/08/09/10
•
Recommend cipher suites.
• R0317/18
•
MUST authenticate.
• R10319/20/21
•
Prohibited cipher suites.
© 2006 Open Grid Forum
4
Approach to Security
Target
Genesis II Unicore
Globus
GridSAM
WSRF BP
?
X
X
SBP Core
X
X
X
?
SP SC
?
X
X
?
XX
X
X
?
WS-Naming
• Everyone use Secure Channel
5
NAREGI
?
• Proposal:
© 2006 Open Grid Forum
Univa
WS-Naming: U-WS-Endpoint
Test Targets
Test Scenario
• R0301
•
• Hard to test!
R0302 and R0303 are
mandatory.
• ???
• R0302
•
Information required for
unambiguous routing to the
right endpoint.
• R03??
•
Route all messages to the
unique endpoint.
© 2006 Open Grid Forum
6
WS-Naming: EPI
Test Targets
Test Scenario
• R0421
•
•
• Build a single client as a
ping service
Sender may send an Endpoint
Identifier (EPI) in the SOAP
header.
EPI MUST be IRIs.
• Endpoint sends EPR to
client
• Client sends back a simple
message:
• R0422
•
Receiver must not rely on this
identifier for routing.
• With EPI in header
• Without EPI in header
• R0423
•
• Verify that the same entity
was contacted.
EPIs Must be in the specified
element within the Metadata
element of the EPR.
© 2006 Open Grid Forum
7
WS-Naming: EPI Address
Test Targets
Test Scenario
• R0431
•
• Build a single client as a
ping service
Must meet Unambiguous Web
Service Endpoint Profile.
• Endpoint sends EPR to
client
• Client sends back a simple
message to the Address.
• Verify that the same entity
was contacted.
• R0432
•
All information necessary
MUST be in the ws:Address.
• R0433
•
The ws:Address MUST be an
EPI.
© 2006 Open Grid Forum
8
WS-Naming: Resolvers
Test Targets
Test Scenario
• R0511/2
•
• Build a single client as a
ping service
One of the two interfaces
MUST be implemented.
• Endpoint sends EPR to
client
• Client sends back a simple
message to the endpoint.
• R0521/2
•
Multiple instances of each type
allowed in EPR.
• R0523/4
•
• Success
These EPR MUST in in the
specified element in the
ws:Metadata element of the
EPR.
© 2006 Open Grid Forum
• Client sends back a simple
message to the endpoint.
• Failure
• Client uses resolver
• Second attempt succeeds
9
OGSA WSRF Basic Profile
• Address
•
• Notification
•
•
MUST use EPRs
• Resource Properties
•
•
•
•
•
•
ResourcePropertyNames
FinalWSResourceInterface
WSResourceInterfaces
ResourceEndpointReference
•
•
•
Support for Destroy
Support for SetTerminationTime
• Base Faults
GetResourceProperty
GetMultipleResourceProperties
QueryResourceProperties
• MUST support Xpath
queries
© 2006 Open Grid Forum
Support Notify
• Lifetime
• Resource Properties
Operations
•
•
•
Support Subscribe
Support Property Change
Notification
Don’t support UseRaw
Must support Simple and Xpath
subscription
•
10
Must support Base Faults