This repository has been archived by the owner on Mar 12, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 20
Python script configuration
ccacciari edited this page Jan 2, 2018
·
7 revisions
The following configuration files are placed in /opt/eudat/b2safe/conf :
- authz.map.json: it contains the assertions for the authorization mechanism
{
"assertion 1":
{ "subject":
[ "jack, james, master*" ],
"action":
[ "read" ],
"target":
[ "*" ]
}
}
the subject list can include iRODS user names, who are authorized to execute the actions listed in the action list against the targets of the target list. The wild character "*" is supported.
- credentials: they are the credentials for the python client which is the bridge between the B2SAFE and the PID registry
{
"handle_server_url": "https://epic.sara.nl:8001",
"private_key": "/opt/eudat/b2safe/conf/330_XXX_USER1_privkey.pem",
"certificate_only": "/opt/eudat/b2safe/conf/330_certificate_only.pem",
"prefix": "XXX",
"handleowner": "200:0.NA/XXX",
"reverselookup_username": "XXX",
"reverselookup_password": "ZZZZZZZZ",
"HTTPS_verify": "/opt/eudat/b2safe/conf/TERENA-SSL-CA-3_bundle.crt"
}
The reverselookup_username, the reverselookup_password and the prefix are provided by the PID registry service provider.
-
log.manager.conf: this is the configuration for the logging mechanism
{ "log_level": "DEBUG", "log_dir": "/srv/irods/current/modules/B2SAFE/log" }
-
msgManager.conf: this is for the experimental message management feature, which is disabled by default
# section containing the logging options
[Logging]
# possible values: INFO, DEBUG, ERROR, WARNING, CRITICAL
log_level=INFO
log_file=/var/log/irods/messageManager.log
[Connector]
#key=lkjhsdf87304wrjf93w84ryowjdf0923038kkkk3
key=
#endpoint=https://messaging-devel.argo.grnet.gr/v1/projects/EUDAT2020
endpoint=