Download HiLA User Guide

HiLA User Guide
12
# Demo 1
hila.unicore6.profile.demo1.keystore = /home/demo/.hila2/demo1.jks
hila.unicore6.profile.demo1.alias = demo1
hila.unicore6.profile.demo1.password = the!user
# Demo 2
hila.unicore6.profile.demo2.keystore = /home/demo/.hila2/demo2.jks
hila.unicore6.profile.demo2.alias = demo2
hila.unicore6.profile.demo2.password = the!user
The multi-user configuration depends on the existance of an implementation of the Config
interface. This can be configured via the hila.unicore6.config property. The default
value for this property is
eu.unicore.hila.grid.unicore6.security.SimpleProfileConfig, which
can use profiles as configured above. If you want to use any of the configured profiles, then the
profile name needs to be added to the HiLA Location of the resources, e.g. unicore6:/demo1@sites
or unicore6:/demo2@sites will use the keystores as configured above. Note that this
does not have anything to do with trust delegation, each of the profile configurations will be
used as primary identities to access Grid resources.
Trust Delegation
In order to use trust delegation, you need to use a different implementation of the Config
interface. The unicore.properties file should contain the following line:
hila.unicore6.config = eu.unicore.hila.grid.unicore6.security. ←TDConfig
TDConfig requires SAML assertions in the directory ~/.hila2/saml-assertions.
SAML assertions can be generated e.g. using the UNICORE Commandline Client (UCC)
and its issue-delegation command. HiLA as an API does not offer this functionality
at the moment. Trust delegation in HiLA is usually used in locations where the user credentials
needed for creating the delegation are not available. Thus, HiLA as the receiver of such SAML
assertions does not require this functionality.
6.2
EMI Execution Services
The EMI Execution Services (EMI-ES) specification [emies] is an agreement among European
middleware providers Arc, gLite, and UNICORE, to offer a common interface to their compute
elements (CEs), which is the equivalent of a HiLA Site.
Starting with version 2.3.0, HiLA supports this specification and can send jobs to EMI-ES
endpoints.