Job execution: Interoperability scenario

1
Job execution Interoperability scenario

• Mike Mineter
• m.mineter_at_ed.ac.uk
• TOE-NeSC, Edinburgh

SLIDES From Morris Riedel, OMII-Europe training
for D-Grid
2
VOMS in Interoperability Scenario WISDOM
SAML- based Attribute Authority (AA) VOMS gets
central role middleware independent
3
CREAM-BES SAML VOMS

• CREAM-BES Support SAML-based VOMS authorization
• Developed by
• gJAF Framework usesSAML assertions to grantor
  deny access

http//www.unicore.eu
4
SAML-based VOMS Support in UNICORE 6

• Used in conjunction withAuthZ Attribute Exchange
  Profile (OGF AuthZ group)to obtain a SAML
  assertionfrom a Policy Information Point (PIP)
• SAML assertions are transported in the
  SOAPheader during WS calls
• E.g. WS-Security Extensions
• Developed by

http//www.unicore.eu
5
XACML Support in UNICORE 6

• XACML is an open standard from OASIS
• Allows to define policies that grant/deny access
  to UNICORE
• Before the XNJS reallyexecutes something an
  XACML callout is performed
• Used in UNICORE in conjunction with
  SAMLassertions
• Developed by

http//www.unicore.eu
6
Available Components of this Scenario (1)

• CREAM-BES (gLite) released in OMII Europe
  repository
• http//repository.omii-europe.org/projects/

7
Available Components of this Scenario (2)

• SAML VOMS released in OMII Europe repository
• http//repository.omii-europe.org/projects/

8
Available Components of this Scenario (3)

• SAML-based VOMS Support and OGSA-BES for UNICORE
  6 released in OMII Europe repository
• http//repository.omii-europe.org/projects/
• Also released on the UNICORE_at_SourceForge platform
• http//www.unicore.eu