Information Technology Reference
In-Depth Information
4.3.1 Security Management
—
Credential Handling
User credentials (proxies or SAML assertions) are handled by the proxy cache
using the JSDL extension that identi
es the virtual organization (VO) where the job
should be executed. Based on the user and VO identi
ers, the proxy cache service
of DCI Bridge downloads the authentication
cate service of
WS-PGRADE (see Chap.
6
). Depending on the type of the authentication
file from the certi
file the
following actions will be executed:
User login/password: no action is required.
SAML: Expiration time is checked.
X509: Expiration time is checked, and if it is for gLite then the Virtual Orga-
nization Membership service (VOMS) extension needed for the VO is added
based on the information in JSDL
file.
Secure Shell (SSH) key: no action is required.
If any problem occurs an error message is placed in the error log. If the
authentication
le is
placed into the proxy cache and the job receives this information. Storing the
processed authentication
file check is successful, then the processed authentication
file in the proxy cache reduces the time of further
authentication checks of new jobs having the same user
VO pair in their JSDL.
-
4.3.2 Input File Management
Input
file management can be done at two places. The generic solution is to do it
inside the DCI Bridge, but for optimization purposes this activity can be postponed
and executed by special wrappers in the target DCI resources. In the latter case, the
DCI Bridge administrator should set this optimization parameter provided that the
required firewall conditions are met. In this case, there is no need for file man-
agement activities in the DCI Bridge. This is also the case when the user speci
ed
remote
file access for the job.
In the generic case, JSDL contains the description of the required input
files, and
the input queue service inside the plugin manager downloads the input
files to the
job temporary directory, either from the storage service of gUSE or from an HTTP
server. At this point the job is prepared to be submitted to the target DCI, and hence
the job is placed into the submit queue of the plugin manager.
4.3.3 Job Submission and Execution
Jobs in the submit queue are already prepared for the target DCI with all the
information needed to submit there, and hence the submission is a straightforward
Search WWH ::
Custom Search