dgca-verifier-service | Repository for the dgca verifier service
kandi X-RAY | dgca-verifier-service Summary
kandi X-RAY | dgca-verifier-service Summary
dgca-verifier-service is a Java library. dgca-verifier-service has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.
This repository contains the source code of the Digital Green Certificates Verifier Service. The DGC Verifier Service is part of the national backends and caches the public keys that are distributed through the DGCG. It is accessed by the DGC Verifier Apps (Android, iOS) to update the key store periodically.
This repository contains the source code of the Digital Green Certificates Verifier Service. The DGC Verifier Service is part of the national backends and caches the public keys that are distributed through the DGCG. It is accessed by the DGC Verifier Apps (Android, iOS) to update the key store periodically.
Support
Quality
Security
License
Reuse
Support
dgca-verifier-service has a low active ecosystem.
It has 15 star(s) with 18 fork(s). There are 5 watchers for this library.
It had no major release in the last 12 months.
There are 5 open issues and 27 have been closed. On average issues are closed in 19 days. There are 1 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of dgca-verifier-service is 1.0.5
Quality
dgca-verifier-service has no bugs reported.
Security
dgca-verifier-service has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
dgca-verifier-service is licensed under the Apache-2.0 License. This license is Permissive.
Permissive licenses have the least restrictions, and you can use them in most projects.
Reuse
dgca-verifier-service releases are available to install and integrate.
Build file is available. You can build the component from source.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi has reviewed dgca-verifier-service and discovered the below as its top functions. This is intended to give you an instant insight into dgca-verifier-service implemented functionality, and help decide if they suit your requirements.
- Download trusted issuers
- Convert trusted issuer entity to Trusted issuer entity
- Gets the current ETag
- Method to update the trusted issuers in the database
- Download certificates
- Method to create Singer information entity from a trust list item
- Get a list of valid kid from all certificates
- Update the signer information of trusted certificates
- Get a delta list from all certificates that have been modified
- Get the delta state of the certificates
- Parse the if - modified -Since -Since header
- Wraps an exception in a JSON object
- Get the status
- Handles a BadRequestException
- Get the status
- Gets a list of trusted issuers
- Get all trusted issuers matching the specified etag
- Lookup the certificate data for the certificate
- Gets raw certificate data
- Get the signer certificate
- Get certificate by resume token
- The main method
- Configure the API
- Get all certificates ids
- Returns the current context for the verifier
Get all kandi verified functions for this library.
dgca-verifier-service Key Features
No Key Features are available at this moment for dgca-verifier-service.
dgca-verifier-service Examples and Code Snippets
Community Discussions
No Community Discussions are available at this moment for dgca-verifier-service.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install dgca-verifier-service
Whether you cloned or downloaded the 'zipped' sources you will either find the sources in the chosen checkout-directory or get a zip file with the source code, which you can expand to a folder of your choice. In either case open a terminal pointing to the directory you put the sources in. The local build process is described afterwards depending on the way you choose. Building this project is done with maven. All required dependencies will be downloaded, the project build and the artifact stored in your local repository. Note: Leave the path as is and only change the file names, as the certs folder will be mapped to this folder inside the docker container. After all containers have started, you will be able to reach the service on your local machine under port 8080.
Check settings.xml in the root folder of this git repository as example. Copy the servers to your own ~/.m2/settings.xml in order to connect the GitHub repositories we use in our code. Provide your GitHub username and access token (see GitHub Help) under the variables suggested.
Run the following command from the project root folder
Perform maven build as described above
Place the keys and certificates named above into the certs folder.
Adjust the values in the docker-compose.yml file to fit the url for the gateway you use and your keys and certificates you have to access it. - DGC_GATEWAY_CONNECTOR_ENDPOINT=https://dgc-gateway.example.com - DGC_GATEWAY_CONNECTOR_TLSTRUSTSTORE_PATH=file:/ec/prod/app/san/dgc/tls_trust_store.p12 - DGC_GATEWAY_CONNECTOR_TLSTRUSTSTORE_PASSWORD=dgcg-p4ssw0rd - DGC_GATEWAY_CONNECTOR_TLSKEYSTORE_ALIAS=1 - DGC_GATEWAY_CONNECTOR_TLSKEYSTORE_PATH=file:/ec/prod/app/san/dgc/tls_key_store.p12 - DGC_GATEWAY_CONNECTOR_TLSKEYSTORE_PASSWORD=dgcg-p4ssw0rd - DGC_GATEWAY_CONNECTOR_TRUSTANCHOR_ALIAS=ta - DGC_GATEWAY_CONNECTOR_TRUSTANCHOR_PATH=file:/ec/prod/app/san/dgc/trust_anchor.jks - DGC_GATEWAY_CONNECTOR_TRUSTANCHOR_PASSWORD=dgcg-p4ssw0rd
Run the following command from the project root folder
Check settings.xml in the root folder of this git repository as example. Copy the servers to your own ~/.m2/settings.xml in order to connect the GitHub repositories we use in our code. Provide your GitHub username and access token (see GitHub Help) under the variables suggested.
Run the following command from the project root folder
Perform maven build as described above
Place the keys and certificates named above into the certs folder.
Adjust the values in the docker-compose.yml file to fit the url for the gateway you use and your keys and certificates you have to access it. - DGC_GATEWAY_CONNECTOR_ENDPOINT=https://dgc-gateway.example.com - DGC_GATEWAY_CONNECTOR_TLSTRUSTSTORE_PATH=file:/ec/prod/app/san/dgc/tls_trust_store.p12 - DGC_GATEWAY_CONNECTOR_TLSTRUSTSTORE_PASSWORD=dgcg-p4ssw0rd - DGC_GATEWAY_CONNECTOR_TLSKEYSTORE_ALIAS=1 - DGC_GATEWAY_CONNECTOR_TLSKEYSTORE_PATH=file:/ec/prod/app/san/dgc/tls_key_store.p12 - DGC_GATEWAY_CONNECTOR_TLSKEYSTORE_PASSWORD=dgcg-p4ssw0rd - DGC_GATEWAY_CONNECTOR_TRUSTANCHOR_ALIAS=ta - DGC_GATEWAY_CONNECTOR_TRUSTANCHOR_PATH=file:/ec/prod/app/san/dgc/trust_anchor.jks - DGC_GATEWAY_CONNECTOR_TRUSTANCHOR_PASSWORD=dgcg-p4ssw0rd
Run the following command from the project root folder
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page