[#75] Update README.md

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.yml` 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`

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.yml` 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.yml` 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`.