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.
In order to configure the credentials to be used for a particular service, follow these steps (see Figure 12):
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:
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
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