kych

OAuth 2.0 API for Swiyu to enable Taler integration of Swiyu for KYC (experimental)
Log | Files | Refs | Submodules | README | LICENSE

application-kych.yml.template (2689B)

      1 # Development configuration for the SWIYU Generic Verifier, used by ./run.sh.
      2 #
      3 # Copy to application-kych.yml and fill in the three values from your SWIYU
      4 # onboarding.  ./run.sh passes this file to Spring Boot as an additional
      5 # configuration location, so it overrides the application.yml inside the
      6 # upstream tree without that tree having to be touched.
      7 #
      8 # This is the development path.  A deployment uses the swiyu-verifier Debian
      9 # package, whose configuration lives in /etc/swiyu-verifier; see
     10 # ../debian/swiyu-verifier.README.Debian.
     11 
     12 application:
     13   # The URL the *wallet* will fetch the request object from.  The wallet
     14   # accepts HTTPS with a publicly trusted certificate only, so for local work
     15   # put a tunnel in front:  ngrok http 8080  and paste its URL here.
     16   external-url: ""
     17 
     18   # Your verifier's DID, and the verification method in its DID document
     19   # whose key signs the authorization requests.
     20   client_id: ""
     21   signing-key-verification-method: ""
     22 
     23   # PEM-encoded EC private key matching that verification method, as a single
     24   # line with literal \n.  A development key can be made with
     25   #   openssl ecparam -name prime256v1 -genkey -noout
     26   signing_key: ""
     27 
     28   # Note: client_id_scheme is gone since the verifier's 4.0.0 release; the
     29   # prefix is now client_id_prefix and defaults to decentralized_identifier.
     30 
     31   # Shown to the user by the wallet when it asks for consent.  "${client-id}"
     32   # inside the file is replaced with the DID above.
     33   client-metadata-file: "file:./client_metadata.json"
     34 
     35 spring:
     36   datasource:
     37     driver-class-name: org.postgresql.Driver
     38     url: "jdbc:postgresql://localhost:5432/verifier_db"
     39     username: "verifier_user"
     40     password: "secret"
     41 
     42   jpa:
     43     hibernate:
     44       # Flyway owns the schema; "validate" only checks it.  Never "create"
     45       # here -- that drops every verification on each start, which is what the
     46       # template this file replaced used to do.
     47       ddl-auto: validate
     48 
     49   flyway:
     50     enabled: true
     51 
     52   docker:
     53     compose:
     54       enabled: false
     55 
     56   mvc:
     57     log-resolved-exception: false
     58 
     59 logging:
     60   level:
     61     ch.admin.bj.swiyu: DEBUG
     62 
     63 springdoc:
     64   show-actuator: true
     65 
     66 webhook:
     67   # KyCH's /notification endpoint.  Running KyCH on a Unix socket, as its own
     68   # development configuration does, means putting a reverse proxy in front of
     69   # it or switching it to SERVE = tcp for this to be reachable.
     70   callback-uri: ""
     71   callback-interval: 5000
     72 
     73 # The claims KyCH needs are in credential_subject_data / dcql_response, which
     74 # this flag controls; it is on by default and listed here as a reminder that
     75 # turning it off breaks KyCH.
     76 application.additional-audit-information.credential-subject-data-enabled: true