Welcome to the Server CLI-Tool Repository.
This repository provides an SDK for generating a server wallet and DID document.
did-cli-tool-server
├── CHANGELOG.md
├── CLA.md
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── LICENSE
├── dependencies-license.md
├── MAINTAINERS.md
├── README.md
├── README_ko.md
├── RELEASE-PROCESS.md
├── SECURITY.md
├── docs
│ └── api
│ ├── CLI-Tool_SERVER_API.md
│ └── CLI-Tool_SERVER_API_ko.md
└── source
├── did-cli-tool-server
│ ├── .gitignore
│ ├── build.gradle
│ ├── gradle
│ │ └── wrapper
│ ├── gradlew
│ ├── gradlew.bat
│ ├── libs
│ ├── README_ko.md
│ ├── README.md
│ ├── settings.gradle
│ └── src
└── releases
└── did-cli-tool-server-1.0.0.jar
Name | Description |
---|---|
source | SDK source code project |
docs | Documentation |
┖ api | API guide documentation |
README.md | Overview and description of the project |
CLA.md | Contributor License Agreement |
CHANGELOG.md | Version-specific changes in the project |
CODE_OF_CONDUCT.md | Code of conduct for contributors |
CONTRIBUTING.md | Contribution guidelines and procedures |
LICENSE | Apache 2.0 |
dependencies-license.md | Licenses for the project’s dependency libraries |
MAINTAINERS.md | General guidelines for maintaining |
RELEASE-PROCESS.md | Release process |
SECURITY.md | Security policies and vulnerability reporting |
: Create a JAR file based on the build.gradle file of this SDK project.
- Open the
build.gradle
file of your project and add a task from the configuration file as shown below.
plugins {
id 'java'
id 'com.github.johnrengelman.shadow' version '7.1.2'
}
repositories {
mavenCentral()
flatDir {
dirs 'libs'
}
}
group = 'org.omnione.did'
java {
sourceCompatibility = JavaVersion.VERSION_17
targetCompatibility = JavaVersion.VERSION_17
}
dependencies {
implementation 'org.bouncycastle:bcprov-jdk18on:1.78.1'
implementation 'com.fasterxml.jackson.core:jackson-databind:2.15.2'
implementation group: 'info.picocli', name: 'picocli', version: '4.2.0'
implementation group: 'com.google.code.gson', name: 'gson', version: '2.8.9'
implementation 'org.hibernate.validator:hibernate-validator:7.0.0.Final'
implementation files('libs/did-datamodel-sdk-server-1.0.0.jar')
implementation files('libs/did-crypto-sdk-server-1.0.0.jar')
implementation files('libs/did-core-sdk-server-1.0.0.jar')
implementation files('libs/did-wallet-sdk-server-1.0.0.jar')
}
shadowJar {
archiveBaseName.set('did-cli-tool-server')
archiveVersion.set('1.0.0')
archiveClassifier.set('')
manifest {
attributes(
'Main-Class': 'org.omnione.did.cli.OmniCLI'
)
}
}
tasks.named('jar').configure {
enabled = false
}
tasks.withType(JavaCompile) {
options.encoding = 'UTF-8'
}
build {
dependsOn shadowJar
}
- Open the
Gradle
tab in IDE and run the project'sTask > Build > Clean and Build
task, or type./gradlew clean build
in a terminal. - Once the execution is complete, the
did-cli-tool-server-1.0.0.jar
file will be generated in the{projetPath}/build/libs/
folder.
Libraries can be found in the Releases.
-
Copy each of the files below to the libs in your server project.
-did-datamodel-server-1.0.0.jar
-did-crypto-sdk-server-1.0.0.jar
-did-core-sdk-server-1.0.0.jar
-did-wallet-sdk-server-1.0.0.jar
-
Add the following dependencies to the build.gradle of the server project.
implementation 'org.bouncycastle:bcprov-jdk18on:1.78.1'
implementation 'com.fasterxml.jackson.core:jackson-databind:2.15.2'
implementation group: 'info.picocli', name: 'picocli', version: '4.2.0'
implementation group: 'com.google.code.gson', name: 'gson', version: '2.8.9'
implementation 'org.hibernate.validator:hibernate-validator:7.0.0.Final'
implementation files('libs/did-datamodel-sdk-server-1.0.0.jar')
implementation files('libs/did-crypto-sdk-server-1.0.0.jar')
implementation files('libs/did-core-sdk-server-1.0.0.jar')
implementation files('libs/did-wallet-sdk-server-1.0.0.jar')
- Sync
Gradle
to ensure the dependencies are properly added.
API Reference can be found here
ChangeLog can be found :
To watch our demonstration videos of the OpenDID system in action, please visit our Demo Repository.
These videos showcase key features including user registration, VC issuance, and VP submission processes.
Please read CONTRIBUTING.md and CODE_OF_CONDUCT.md for details on our code of conduct, and the process for submitting pull requests to us.