| commit | 8596764600ec0a4442a40c85539b867f5d647bc1 | [log] [tgz] |
|---|---|---|
| author | margaretha <margaretha@ids-mannheim.de> | Wed Nov 13 13:35:33 2019 +0100 |
| committer | margaretha <margaretha@ids-mannheim.de> | Wed Nov 13 13:35:33 2019 +0100 |
| tree | 0d15daddb326b9035e9e921bc79677d6436508b1 | |
| parent | 03b195a8144d8ccad75060f0d2b2da5b514a917c [diff] |
Added warnings when requesting non-public fields via the search API with accessRewriteDisabled (resolved #43). Change-Id: I917415f242c1adf884bacb832fd7644cddaa6973
- core/Changes[diff]
- core/pom.xml[diff]
- core/src/main/java/de/ids_mannheim/korap/exceptions/StatusCodes.java[diff]
- core/src/main/java/de/ids_mannheim/korap/service/SearchService.java[diff]
- full/Changes[diff]
- full/pom.xml[diff]
- full/src/test/java/de/ids_mannheim/korap/web/controller/PublicMetadataTest.java[diff]
- lite/Changes[diff]
- lite/pom.xml[diff]
- lite/src/test/java/de/ids_mannheim/korap/web/service/LiteSearchControllerTest.java[diff]
Kustvakt is a user and policy management component for KorAP (Diewald et al., 2016). It manages user access to resources (i.e. corpus data) typically bound with some licensing schemes. The licensing schemes of IDS resources provided through KorAP (DeReKo) are very complex involving the user access location and purposes (Kupietz & Lüngen, 2014). To manage user access to resources, Kustvakt performs query rewriting with document restrictions (Bański et al., 2014).
Kustvakt acts as a middleware in KorAP binding other components, such as Koral a query serializer and Krill a search component, together. As the KorAP's API provider, it provides services, e.g. searching and retrieving annotation data of a match/hit, that can be used by a KorAP client, e.g. Kalamar (a KorAP web user interface) and KorapSRU (the CLARIN FCS endpoint for KorAP).
Versions
Kustvakt lite version
provides basic services including search, match info, statistic and annotation services, without user and policy management.
Kustvakt full version
provides user and policy management and extended services, in addition to the basic services. This version requires a database (Sqlite is provided) and an LDAP system for user authentication.
Recent changes on the project are described in the change logs (Changes files).
Web-services
Web-services including their usage examples are described in the wiki.
Setup
Prerequisites: Jdk 1.8, Git, Maven 3
Clone the latest version of Kustvakt
Since Kustvakt requires Krill and Koral, please install Krill and Koral in your maven local repository according to the required versions specified in Kustvakt/core/pom.xml.
Install Kustvakt-core in your maven local repository
Package Kustvakt full version
The jar file is located in the target/ folder.
Package Kustvakt lite version
The jar file is located in the target/ folder.
Customizing Kustvakt configuration
Copy the default Kustvakt configuration file (e.g. full/src/main/resources/kustvakt.conf or lite/src/main/resources/kustvakt-lite.conf), to the same folder as the Kustvakt jar files (/target). Please do not change the name of the configuration file.
Setting Index Directory
Set krill.indexDir in the configuration file to the location of your Krill index (relative path to the jar). In Kustvakt's root directory, there is a sample index, e.g.
Setting LDAP
Set the location of the LDAP configuration file for Kustvakt full version. The file should contain an admin password to access an LDAP system. Without LDAP, user authentication functions and services cannot be used. Authentication mechanism can be extended by implementing other authentication methods e.g. using a database.
ldap.config = path-to-ldap-password
Setting BasicAuthentication for Testing
For testing, you can use/activate BasicAuthentication, see Spring XML configuration file for testing at /full/src/test/resources/test-config.xml. BasicAuthentication uses a dummy UserDao allowing all users to be authenticated users. You can implement UserDao by connecting it to a user table in a database and checking username and password for authentication.
<bean id="basic_auth" class="de.ids_mannheim.korap.authentication.BasicAuthentication" /> <util:list id="kustvakt_authproviders" value-type="de.ids_mannheim.korap.interfaces.AuthenticationIface"> <ref bean="basic_auth" /> ... </util:list>
Optional Custom Configuration
Changing Kustvakt Server Port and Host
server.port = 8089 server.host = localhost
Setting Default Foundries
The following properties define the default foundries used for specific layers. For instance in a rewrite, a default foundry may be added to a Koral query missing a foundry.
default.foundry.partOfSpeech = tt default.foundry.lemma = tt default.foundry.orthography = opennlp default.foundry.dependency = malt default.foundry.constituent = corenlp default.foundry.morphology = marmot default.foundry.surface = base
Running Kustvakt Server
Requires kustvakt.conf or kustvakt-lite.conf in the same folder as the jar file. Otherwise assuming sample-index located in the parent directory of the jar file.
Kustvakt full version requires an LDAP configuration file containing an admin password to access an LDAP system. You can still run Kustvakt full version without an LDAP system, but user authentication functions and services cannot be used. Only services for guest/demo user would be available.
To run Kustvakt with a custom spring XML configuration file, it must be included in the classpath. For instance: custom-spring-config.xml is located in config folder. The config folder must be included in the classpath with -cp command.
Shutting down Kustvakt Server
Kustvakt server can be shut down by sending a POST request with a shutdown token. When Kustvakt server is started, a shutdown token is automatically generated and written to a shutdownToken file with the following format:
A shutdown request can be sent as follows.
Advanced Setup
Advanced setup such as setting database properties and configuring mail settings for email notifications, are described in the wiki.
License
Kustvakt is published under the BSD-2 License. It is developed as part of KorAP, the Corpus Analysis Platform at the Leibniz Institute for the German Language (IDS), member of the Leibniz Association.
Contributions
Contributions to Kustvakt are very welcome!
Ideally, any contributions should be committed via KorAP Gerrit server to facilitate code reviewing (see Gerrit Code Review - A Quick Introduction). However, we are also happy to accept comments and pull requests via GitHub.
Please note that unless you explicitly state otherwise any contribution intentionally submitted for inclusion into Kustvakt shall – as Kustvakt itself – be under the BSD-2 License.
Publication
Diewald, Nils/Hanl, Michael/Margaretha, Eliza/Bingel, Joachim/Kupietz, Marc/Bański, Piotr/Witt, Andreas (2016): KorAP Architecture – Diving in the Deep Sea of Corpus Data. In: Calzolari, Nicoletta/Choukri, Khalid/Declerck, Thierry/Goggi, Sara/Grobelnik, Marko/Maegaard, Bente/Mariani, Joseph/Mazo, Helene/Moreno, Asuncion/Odijk, Jan/Piperidis, Stelios (Hrsg.): Proceedings of the Tenth International Conference on Language Resources and Evaluation (LREC 2016), Portorož, Slovenia. Paris: European Language Resources Association (ELRA), 2016. S. 3586-3591.
Bański, Piotr/Diewald, Nils/Hanl, Michael/Kupietz, Marc/Witt, Andreas (2014): Access Control by Query Rewriting. The Case of KorAP. In: Proceedings of the Ninth Conference on International Language Resources and Evaluation (LREC’14). European Language Resources Association (ELRA), 2014. S. 3817-3822.
References
Kupietz, Marc/Lüngen, Harald (2014): Recent Developments in DeReKo. In: Calzolari, Nicoletta et al. (eds.): Proceedings of the Ninth International Conference on Language Resources and Evaluation (LREC'14). Reykjavik: ELRA, 2378-2385.