This provider will monitor the life of a remote certificate. It connects to an ssl TCP listener and obtains the certificate from it. If then checks the cert for subject, start date, end data, and email address. All of this information is put in the index if it is successfully obtained. This provider is an execution aggregator provider. These providers are quite useful as is and additionally serve as an example of how to create others. The perl script and configuration file can be modified to the users liking once installed. This provider has a perl script and an xml configuration file. The perl script is used to obtain information and formated the information into xml output. The output is written to stdout where it is gathered and put into the Index Service. The xml file is of a common format that is explained here:

http://www.globus.org/toolkit/docs/4.0/info/aggregator/WS_MDS_Aggregator_Public_Interfaces.html#id2528218

After installing the package the xml configuration files will be copied to $GLOBUS_LOCATION/etc/globus_wsrf_mds_index/default_providers/ where the DefaultIndexService will find them and use them to register the provider.

This is an execution aggregator source based information provider.

2. Prerequisites

A working Perl installation

3. Configuring

The following configuration is required for this information provider:

In order to grant permission to the installed perl scripts the user must edit the file: $GLOBUS_LOCATION/etc/globus_wsrf_mds_index/jndi-config.xml such that the tags:

    <parameter>
          <name>executableMappings</name>
          <value>
              aggr-test=aggregator-exec-test.sh, pingexec=example-ping-exec
          </value>
    </parameter>

includes the new provider. For example:

    <parameter>
          <name>executableMappings</name>
          <value>
              cert-info=cert-check.pl
          </value>
    </parameter>

This provider will monitor the life of a remote certificate. It connects to an ssl TCP listener and obtains the certificate from it. If then checks the cert for subject, start date, end data, and email address. All of this information is put in the index if it is successfully obtained. To change what server is monitored edit the file:
```
GLOBUS_LOCATION/etc/globus_wsrf_mds_index/default_providers/cert-info-reg.xml
```
and change the line:
```
   <RegistrantEPR
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
      xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/03/addressing"
      xmlns:agg="http://mds.globus.org/aggregator/types">
        <wsa:Address>https://www.SITE.COM:8443</wsa:Address>
   </RegistrantEPR>
```
from "https://www.SITE.COM:8443" to the ssl server of your choice.

4. Resource Properties

Data appears as part of the ServiceGroupEntry RP

4.1. Namespace URI

TODO: Include the Namespace URI, or provide a olink to the Java API Documentation, which is required to construct the QName for the subscription to the Topic.

5. Schema

6. Security Considerations

General security considerations associated with the container and all MDS services apply. See: Aggregator Framework.

By default, the aggregator sources do not use authentication credentials -- they retrieve information using anonymous SSL authentication or no authentication at all, and thus retrieve only publicly-available information. If a user or administrator changes that configuration so that a service's aggregator source uses credentials to acquire non-privileged data, then that user or administrator must configure the service's aggregator sink to limit access to authorized users.

7. Testing

N/A

8. Troubleshooting

N/A

Prev		Next
GT 4.1.3 Release Notes: Cert Check Info Information Provider	Home	Glossary