Subsections

Advanced security configuration


The Security Profiles view

This view comes in handy, when a user wants to access multiple Grids at the same time, presenting different credentials to the Grid services in order to authenticate himself. For instance, the user may define which certificate to use for each registry that he wants to access (a UNICORE 6 service registry usually lists all services in a Grid). For each registry, the configured credentials can be automatically passed down to all of its children, i.e. the services that it contains. This way, the selected certificate is also used to access each of the services in the registry (and their children, grand-children etc.).

This mechanism is not restricted to registries but can be applied to each service in the Grid, thus an even more fine-grained security setup is possible.

Figure 12: The Security Profiles view
Image credentials

In order to configure the credentials to be used for a particular service, follow these steps (see Figure 12):

  1. Create a new security profile 1.
  2. Adjust all security settings for this profile to your needs, e.g. select a certificate 2, choose whether a proxy certificate shall be created (only needed for accessing services from other Grid middlewares like Globus).
  3. Use the map to security profile action on the service in the Grid Browser view for creating a new site entry 3.
  4. Select the new profile for the newly created site 4. Alternatively, you can reuse an existing profile and skip the steps 1-2.

Passing down credentials to child services works like this: for each site entry in the lower table of the Security Profiles view, the first column shows a pattern which matches a particular service. Using the wildcard character `*' at the end of the pattern, the service's children will be matched, too. For example, the pattern for a registry called `UNICORE test Grid' looks like this:

$\noindent\colorbox{lightyellow}{\begin{minipage}{20cm}
\begin{alltt}
\relax{} Grid/UNICORE test Grid/*\relax \end{alltt}\end{minipage}}$

Now imagine this registry contains a target system service called `Alpha-Site'. The Grid Browser displays the target system as a child node of the registry node. In order to determine which credentials to use for acessing this service, the path of node names from the target system node up to the top level node (called `Grid') is determined and concatenated to form a single URL (the names are separated by slashes). In our example, this results in

$\noindent\colorbox{lightyellow}{\begin{minipage}{20cm}
\begin{alltt}
\relax{} Grid/UNICORE test Grid/Alpha-Site\relax \end{alltt}\end{minipage}}$

Next, this URL is compared to all patterns that have been defined in the site entries. The longest name path pattern that matches the URL `Grid/UNICORE test Grid/Alpha-Site' (i.e. the pattern that contains the most slashes) determines which security profile is used for the service. In our example, the pattern `Grid/UNICORE test Grid/*' matches (because of the wildcard character).

Note: Due to the fact that the Grid is really a graph of services (not a tree), there can actually be multiple name paths for a given service. In this case, all name paths are matched against all patterns and again, the longest pattern wins. In case of two or more matched patterns with equal length, the choice of the `winning' pattern is arbitrary.

Bastian Demuth
2010-05-25