From 7525123e74576e3c519b45aa480ecbd1cd96302e Mon Sep 17 00:00:00 2001 From: Daniil Palagin Date: Wed, 23 Oct 2024 11:57:37 +0200 Subject: [PATCH] [#75] Update development.md and setup.md --- doc/development.md | 2 +- doc/setup.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/development.md b/doc/development.md index 99a4b0bd..560f2a5c 100644 --- a/doc/development.md +++ b/doc/development.md @@ -4,7 +4,7 @@ Frontend of the application is developed separately. The setup requires the following steps: 1) configure the application according to [Setup Guide](setup.md) -2) configure `config.properties` to contain `security.sameSite=None` +2) configure `application.properties` to contain `security.sameSite=None` This is important if you are running the application over HTTP so web browser would not block requests to the server due to CORS policy. 3) build the backend `mvn clean package` diff --git a/doc/setup.md b/doc/setup.md index 40d32b4b..b170458c 100644 --- a/doc/setup.md +++ b/doc/setup.md @@ -9,7 +9,7 @@ ### Application Configuration -The application uses `src/main/resources/config.properties` to configure: +The application uses `src/main/resources/application.properties` to configure: * connection to internal triple store * REST endpoint of Form service * SMTP configuration for sending emails @@ -54,7 +54,7 @@ SForms service is configured in `formGenServiceUrl`, the call to the service sho ### OpenID Connect Authentication RecordManager can work with an external authentication service implementing the OpenID Connect protocol. To use it, -set the `security.provider` (in `config.properties` or via `SECURITY_PROVIDER` via an environment variable) configuration to `oidc` +set the `security.provider` (in `application.properties` or via `SECURITY_PROVIDER` via an environment variable) configuration to `oidc` and configure the `spring.security.oauth2.resourceserver.jwt.issuer-uri` (in `application.properties` or using an environment variable) parameter to the URI of the OAuth2 token issuer. When using Keycloak, this corresponds to the URI of the realm through which Record Manager users authenticate their requests. For example, the value may be `http://localhost:8080/realms/record-manager`.