 |   | |
| HomePrev | Part I. Introduction | Next |
|---|---|---|
Table of Contents
To prevent sensitive information such as passwords from being logged
in general activity logs, add the following XML chunk to the bottom of
opensrf_core.xml, just inside the <config> section:
...
</routers>
<shared> <!-- new block starts here -->
<log_protect>
<match_string>open-ils.auth.authenticate.verify</match_string>
<match_string>open-ils.auth.authenticate.complete</match_string>
<match_string>open-ils.auth_proxy.login</match_string>
<match_string>open-ils.actor.user.password</match_string>
<match_string>open-ils.actor.user.username</match_string>
<match_string>open-ils.actor.user.email</match_string>
<match_string>open-ils.actor.patron.update</match_string>
<match_string>open-ils.cstore.direct.actor.user.create</match_string>
<match_string>open-ils.cstore.direct.actor.user.update</match_string>
<match_string>open-ils.cstore.direct.actor.user.delete</match_string>
</log_protect>
</shared> <!-- new block ends here -->
</config>Z39.50 server target definitions have been removed from the sample
opensrf.xml.example file. To migrate existing settings from your
opensrf.xml configuration file to the database, peform the
following steps:
First, set up your custom Z39.50 sources in the database. For
each entry in z3950/services, map the following XML paths to the
corresponding config.z3950_source table column as follows:
z3950/services/<entry> = name
//<entry>/name = label
//<entry>/host = host
//<entry>/port = port
//<entry>/db = db
//<entry>/record_format = record_format
//<entry>/transmission_format = transmission_format
Then, for each attribute defined in the <attrs> element for
a given service, map the following XML paths to the corresponding
config.z3950_attr table column as follows:
z3950/services/<entry> = source
//<entry>/attrs/<attr> = name
//<entry>/attrs/<attr>/code = code
//<entry>/attrs/<attr>/format = format
truncation column for the attribute.