blob: fc3234718ade0567cc47b96a09f9dafea1606843 [file] [log] [blame]
Chengyu Fanb25835b2015-04-28 17:09:35 -06001; The catalog section contains settings of catalog
Chengyu Fanf4c747a2015-08-18 13:56:01 -06002general
Chengyu Fanb25835b2015-04-28 17:09:35 -06003{
4 ; Set the catalog prefix, so that adapters can extend it as their own prefix
5 ; e.g., suppose that the catalog has the prefix "ndn:/cmip5", so QueryAdapter has the prefix
6 ; "ndn:/cmip5/catalog/query" and "ndn:/cmip5/catalog/query-results",
7 ; PublishAdapter has the prefix "ndn:/cmip5/catalog/publish"
8
9 prefix /catalog/myUniqueName
Chengyu Fan92440162015-07-09 14:43:31 -060010
Chengyu Fanf4c747a2015-08-18 13:56:01 -060011 ; Set name components for the scientific data, for example, the climate data
12 ; contains name fields like activity, ..., time
Chengyu Fan92440162015-07-09 14:43:31 -060013 nameFields activity,product,organization,model,experiment,frequency,modeling_realm,variable_name,ensemble,time
Chengyu Fanf4c747a2015-08-18 13:56:01 -060014
15 ; Set the database table name for the scientific data
16 databaseTable cmip5
Chengyu Fanb25835b2015-04-28 17:09:35 -060017}
18
19; The queryAdapter section contains settings of queryAdapter
20queryAdapter
21{
Chengyu Fanf4c747a2015-08-18 13:56:01 -060022 ; ; Set the Identity that signs data that respond the queries
23 ; ; If the identity contains multiple keys, use the default one
24 ; signingId ndn:/cmip5/test/query/identity
Chengyu Fanb25835b2015-04-28 17:09:35 -060025
Chengyu Fanf4c747a2015-08-18 13:56:01 -060026 ; Set the filter category names, for example,
27 ; the filter category contains name fields like activity, ..., ensemble
28 filterCategoryNames activity,product,organization,model,experiment,frequency,modeling_realm,variable_name,ensemble
29
30 ; Set database settings for QueryAdapter
Chengyu Fanb25835b2015-04-28 17:09:35 -060031 database
32 {
33 dbServer 127.0.0.1 ; Specify the database server
34 dbName testdb ; Specify the database name
35 dbUser testuser1 ; Specify the database user name
36 dbPasswd test123 ; Specify the associated password for the dbUser
37 }
38}
39
40; The publishAdapter section contains settings of publishAdapter
41publishAdapter
42{
Chengyu Fanf4c747a2015-08-18 13:56:01 -060043 ; Set the Identity that signs data that respond the queries
44 ; If the identity contains multiple keys, use the default one
45 ; signingId ndn:/cmip5/test/query/identity
Chengyu Fanb25835b2015-04-28 17:09:35 -060046
Chengyu Fanf4c747a2015-08-18 13:56:01 -060047 ; The security section contains the rules for the adapter to verify the
48 ; published files indeed come from a valid publisher.
Chengyu Fanc7b87ad2015-07-09 16:44:37 -060049 ; security
Chengyu Fanb25835b2015-04-28 17:09:35 -060050 ; {
Chengyu Fanc7b87ad2015-07-09 16:44:37 -060051 ; rule
52 ; {
53 ; id "NDN Hierarchy Test Rule"
54 ; for data ; rule for Data (to validate NDN certificates)
55 ; filter
56 ; {
57 ; type name ; condition on data name
58 ; regex ^(<>*)$
59 ; }
60 ; checker
61 ; {
62 ; type hierarchical ; the certificate name of the signing key and
63 ; ; the data name must follow the hierarchical model
64 ; sig-type rsa-sha256 ; data must have a rsa-sha256 signature
65 ; }
66 ; }
67 ; trust-anchor
68 ; {
69 ; type file
70 ; file-name /directory/to/the/root.ndncert ; the file name, by default this file should be
71 ; ; in same folder as this config file.
72 ; }
Chengyu Fanb25835b2015-04-28 17:09:35 -060073 ; }
74
75 ; The database section contains settings of database
76 ; The user in publishAdapter may differ from the one in queryAdapter, to provide different
77 ; access control
78 database
79 {
80 dbServer 127.0.0.1 ; Specify the database server
81 dbName testdb ; Specify the database name
82 dbUser testuser2 ; Specify the database user name
83 dbPasswd test123 ; Specify the associated password for the dbUser
84 }
85
86 ; The sync section contains settings of ChronoSync
87 sync
88 {
89 ; Set the prefix for sync messages, default 'ndn:/ndn/broadcast'
Chengyu Fanf4c747a2015-08-18 13:56:01 -060090 prefix /ndn/broadcast
Chengyu Fanb25835b2015-04-28 17:09:35 -060091
Chengyu Fanf4c747a2015-08-18 13:56:01 -060092 ; The sync_data_security section contains the rules that are required for ChronoSync nodes to
93 ; verify published data by other ChronoSync nodes.
94 ; The ChronoSync validator will be disabled when sync_data_security section is missing.
95
Chengyu Fanb25835b2015-04-28 17:09:35 -060096 ; sync_data_security
97 ; {
Chengyu Fanf4c747a2015-08-18 13:56:01 -060098 ; ; This section defines the trust model for the ChronoSync data Management. It consists of
99 ; ; rules and trust-anchors, which are briefly defined in this file. Multiple rules can be
100 ; ; included
Chengyu Fanb25835b2015-04-28 17:09:35 -0600101 ; ; rule
102 ; ; {
103 ; ; id "ChronoSync Update Messages Rule"
104 ; ; for data ; rule for Data (to validate NDN certificates)
105 ; ; filter
106 ; ; {
107 ; ; type name ; condition on data name
108 ; ; regex ^[^<KEY>]*<KEY><>*<ksk-.*><ID-CERT><>$
109 ; ; }
110 ; ; checker
111 ; ; {
112 ; ; type hierarchical ; the certificate name of the signing key and
113 ; ; ; the data name must follow the hierarchical model
114 ; ; sig-type rsa-sha256 ; data must have a rsa-sha256 signature
115 ; ; }
116 ; ; }
117 ; ; trust-anchor
118 ; ; {
119 ; ; type file
120 ; ; file-name keys/default.ndncert ; the file name, by default this file should be placed in
121 ; ; ; the same folder as this config file.
122 ; ; }
123 ; }
124 }
125}