GCube Security Model

This page describes the security model adopted in the DILIGENT infrastructure

Authentication Model

The DILIGENT Security model uses Public Key Infrastructure (PKI) mechanisms to authenticate identities acting in the infrastructure. Each authenticated invocation must be performed using valid credentials issued by a trusted Certification Authority (CA).

To speed up performances of some Running Instances (RI) unauthenticated invocatons are also allowed, even if not planned in the design of DILIGENT security. These invocations can be performed without any credentials, neither authentication nor authorization are enforced in these cases.

Authentication Mechanism

The mechanism used in DILIGENT to authenticate RI invocatons is the WS-SecureConversation one. The Java WS-Core container provides a built-in implementation of this standard called GSI-SecureConversation.

This choice is driven by the need to delegate caller credentials to invoked RI. The HTTPS mechanism (also available in the Java-WS-Core) cannot interoperate with the GSI-SecureConversation one, thus preventing the exploiting of both mechanisms in the DILIGENT infrastructure. For this reason the HTTPS mechanism has been discarded.

Authorization Mechanism

Authorization rights for each Digital Library (DL) are managed separately. A VOMS server maintains the DL hierarchy as a VOMS groups hierarchy. Roles are defined globally in DILIGENT and are granted to users in a DL (thus in a VOMS group). When a user log in the portal fresh proxy credentials are created for it. These credentials contains roles held by the user during session. As a VOMS design choice, all groups the user is member of are always included in a proxy certificate when the VOMS is contacted. Role/s held by the user in a group need to be explicitly required by the user at proxy creation.

The DL context

Authenticated invocations to DILIGENT RI are performed in the context of a DL. The context is identified from the proxy certificate attached to the request. The user is supposing to operate in the DL corresponding to the VOMS group that contains at least a role in the proxy credentials.

As a consequence of this choice in DILIGENT all roles included in a proxy certificate must be bound to the same group. This allows to uniquelly identify the VOMS group where the user is acting and thus the corresponding DL. This of course does not work for unauthenticated invocations.

Identities for DILIGENT services

DILIGENT RI need certificates in order to:

• Autonomously operates in the infrastructure
• Perform further service calls (serving a request) without the need to impersonate the caller

The Delegation and Credentials Renewal services developed in DILIGENT allows RI to periodically receive fresh credentials to perform invocations.

Alongside functonalities provided by these services, the delegation mechanism built-in into the GSISecureConversation protocol is also available. It allows a RI to impersonate the caller, if the caller allows to delegate their credentials to the RI itself.

Two scenarios can be foreseen for DILIGENT RI credentials:

Identity of RI acting in a Single DL

These RIs needs to act in a single DL, thus they need only a single copy of credentials containing roles for that DL.

These RIs can also support unauthenticated incoming requests, as they always operate in the infrastructure using the same identity.

Identity of RI acting in mutiple DLs

These RIs needs to act in mulltiple DLs, thus they need different identities ( one for each DL where they operate). Moreover they need to select right credentials to use for RI invocations. This choice is driven by the DL where the caller is operating. This DL can be identified from the caller certificate (see The DL context section)

For this reason these RIs cannot support unauthenticated incoming requests, as they need to know in which DL the caller is operating.

DILIGENT services can also adapt their behaiour to one of scenarios described above depending on the deployment configuration. This can be done exploiting the XXX functionality of the Node Access Library.