Closed because duplicate
https://dart.dev/overview

• Okapi (trinsic-id/okapi#319)
• SDK

Describe the bug
Build Documentation github actions is failing

To Reproduce
See https://github.com/trinsic-id/sdk/actions/workflows/docs.yml

Expected behavior
Deploy docs successfully

• Okapi
• SDK

Objective

Expand support of Okapi and Trinsic SDK for Python.

Solution

This port should leverage the Okapi stack and gRPC tools for Python as the foundation of the library. The effort required can be roughly separated in two phases:

• Python support for Okapi
• Python support for Trinsic SDK

The library should follow naming guidelines established by existing libraries, but in a way that's idiomatic to Python.

Tracking Effort

• Python wrapper for Okapi - this wrapper should deliver functionality that will allow Okapi to be used in Python on any platform. Initial work has been started using the old library name "didcomm-grpc". Okapi uses Protobuf as data contract for the the FFI layer, but does not use any gRPC functionality. This library will invoke existing native library built in Rust.
  • Basic Unit tests - generate key, sign message, etc. trinsic-id/okapi#50
  • Build Pipeline - provide GH action that builds and run the tests trinsic-id/okapi#53
  • Package Publishing - GH action that publishes packages to PyPI. This action should be a separate job in the exist build pipeline. It should trigger from a release event (already setup) and use the build native libraries (windows, linux, macos) to provide support for all platforms
• Trinsic SDK - leverages Okapi as main dependency and builds support for profile management and gRPC service invocation.
  • Basic unit tests - these tests should be runnable manually against a running ecosystem stack. Currently, we run the locally against localhost, but soon we will be able to run the tests as part of CI. For this purpose, tests should be parametrized and accept Ecosystem Server URL.
  • Build Pipeline - provide GH action that builds and run the tests
  • Package Publishing - GH action that publishes packages to PyPI.
• Release github action to deploy to PyPI.

The issue and generate-proofcommands that wrap the returned json objects for signed credentials and generated proofs in "json": "JsonStruct": {...}. Because of this new data model, if a user inserts the vaccination-certificate-signed.json directly into their wallet without first editing the json, the generate-proof command will throw an error unless the signed credential is first manually taken out of the json objects it's wrapped by.

Loom video of repro steps: https://www.loom.com/share/836992da7801493ba0186018be66641e

Example of output of issue command:

"json": {
    "JsonStruct": {
      "proof": {
        "type": "BbsBlsSignature2020",
        "created": "2021-11-21T21:10:46Z",
        "verificationMethod": "did:key:z5TcFNEkpGAHjoJydEGLXKgkzXgJdFGtUKHwNKNmi8xwnd8sAmfFGnLoyhy5EG1v9Y9Y5rV9cKHdTDzm4ozQ32iS5znt5vx5FqtwRKTX8at2x1ZKHMfsEME9jT62k4g1dPPmW3R71s7pqkPQMG9dScv65escSv3Ki8fG3HSmZ4JQrbSGjNRLG5nGc1pBqvUmxXVbhzWfT#zUC74ou5VcpG4Mag9t6iU9Cpt1T3X7WnHzxefd9QYeBhsD5qT7HREjrLNfTjQCed2QuiN7M1HJW1x6ynrxhnxgHytW9375xJ8MuyGyyxJAVCxbCGQPZ5LVWtKmZtZJNP55hPGDo",
        "proofPurpose": "assertionMethod",
        "proofValue": "hNDZ2Pp/CS4cBW1bpNZa1FybVxPAGIRjy4i1oRhAVFsEIq82GNxuJXK96iMsBOahGcP2ZgEemW1VF+KqxBWAmf3NVI+Jl5/iisnWjfeUKA0mxmR4aV6eZW6dLqwQ3OW45LwoClX3ERVPXjryOuDEJg=="
      },
      "issuer": "did:key:zUC724vuGvHpnCGFG1qqpXb81SiBLu3KLSqVzenwEZNPoY35i2Bscb8DLaVwHvRFs6F2NkNNXRcPWvqnPDUd9ukdjLkjZd3u9zzL4wDZDUpkPAatLDGLEYVo8kkAzuAKJQMr7N2",
      "type": [
        "VaccinationCertificate",
        "VerifiableCredential"
      ],
      "description": "COVID-19 Vaccination Certificate",
      "issuanceDate": "2019-12-03T12:19:52Z",
      "@context": [
        "https://www.w3.org/2018/credentials/v1",
        "https://w3id.org/vaccination/v1",
        "https://w3id.org/security/bbs/v1"
      ],
      "credentialSubject": {
        "batchNumber": "1183738569",
        "countryOfVaccination": "US",
        "type": "VaccinationEvent",
        "id": "urn:uuid:c53e70f8-ce9a-4576-8744-e5f85c20a743"
      },
      "name": "COVID-19 Vaccination Certificate",
      "expirationDate": "2029-12-03T12:19:52Z",
      "id": "urn:uvci:af5vshde843jf831j128fj"
    }
  }
}

Example of output from generate-proof command

{
  "json": {
    "JsonStruct": {
      "credentialSubject": {
        "id": "urn:uuid:c53e70f8-ce9a-4576-8744-e5f85c20a743",
        "countryOfVaccination": "US",
        "type": "VaccinationEvent",
        "batchNumber": "1183738569"
      },
      "id": "urn:uvci:af5vshde843jf831j128fj",
      "@context": [
        "https://www.w3.org/2018/credentials/v1",
        "https://w3id.org/vaccination/v1",
        "https://w3id.org/security/bbs/v1"
      ],
      "proof": {
        "verificationMethod": "did:key:z5TcFNEkpGAHjoJydEGLXKgkzXgJdFGtUKHwNKNmi8xwnd8sAmfFGnLoyhy5EG1v9Y9Y5rV9cKHdTDzm4ozQ32iS5znt5vx5FqtwRKTX8at2x1ZKHMfsEME9jT62k4g1dPPmW3R71s7pqkPQMG9dScv65escSv3Ki8fG3HSmZ4JQrbSGjNRLG5nGc1pBqvUmxXVbhzWfT#zUC74ou5VcpG4Mag9t6iU9Cpt1T3X7WnHzxefd9QYeBhsD5qT7HREjrLNfTjQCed2QuiN7M1HJW1x6ynrxhnxgHytW9375xJ8MuyGyyxJAVCxbCGQPZ5LVWtKmZtZJNP55hPGDo",
        "nonce": "7XacY2OnNJTEncXRc0eWHG4qChwaFNA/VamhzvZ73mbTQVu8h/FKQ44v2kei9s5Ca+8=",
        "type": "BbsBlsSignatureProof2020",
        "created": "2021-11-21T21:10:46Z",
        "proofPurpose": "assertionMethod",
        "proofValue": "AA9Of4QhOXGFDNWP3Ty+oDKDJUKxDOjo+oqvD4mOQ+RiTn8T3JROwtOpksfqDi7c4L12VowE3yGJPzRjZvo11gDA4XcqDp3PmxVd3Nmbergu+U3fberVR7M1fUaQPyIqiQPL9aUHlBhcX219a795+GLyQFKh1nHEOS3rSfaXBi0E4llxKdauo/ST1JEaMB2rW/VbygAAAHSXzUu/auqtTatF7qKILH5T+7DkjmaqG0EZ3RF5fsq36vGAQ7FSfRT220D9xBEOipgAAAACbViLwIv62Qk0zSeXz2xFt8vDIdB14nl3U/z46x5YLwhEju3JL2xuMxkqMBrneLQ4ts8vJR9eIK9ItfSC0ZG9b4NTE/meAKbXUNMTaFF5b/aC0u1R0/CC8i8O2YMh3aFLq+OlfhlETdtHxD/TtWaGUgAAAAZz3IrNTpUKV9Ae6wE+TKDHHtqfMI0cSXDDh/EgG0HwXh6vidOHQsarqYGv9PqRHL73E7PzglAVzuAMN4anpyplBPDGJ5vfcXtzb/3k4uTpAnM0jZ1tn87BC/MwoDVzeu5jmkk2wUvC1NpFTy2DQl2uX6WCH8qgskHW0qEIXBFKQGEOSfdl2fh5iDxixdk8Rf1b1bh98b4j6g026PS74iw8C1tghnAgLB3fSaOpJMZnHcSDb1FAWvKO9hj/YQgNhxo="
      },
      "issuer": "did:key:zUC724vuGvHpnCGFG1qqpXb81SiBLu3KLSqVzenwEZNPoY35i2Bscb8DLaVwHvRFs6F2NkNNXRcPWvqnPDUd9ukdjLkjZd3u9zzL4wDZDUpkPAatLDGLEYVo8kkAzuAKJQMr7N2",
      "type": [
        "VaccinationCertificate",
        "VerifiableCredential"
      ]
    }
  }
} 

Expected Behavior
Credentials and Proofs are returned as the top level json object

• C#
• Python
• Javascript - Node
• Javascript - Browser
• Add automated testing to pipeline

• All the credential template calls are missing from the CLI
• the register-egf call is also missing

• Java support
  • Okapi
  • Services

Updates required for all SDK

• Change default endpoint to prod.trinsic.cloud:443 with TLS support
  • Node
  • Browser
  • Python #184
  • Go #200
  • NET
  • Swift
  • Java #187
  • Android - covered by Java already
  • Ruby

Additionally, it is recommended that SDKs take a configuration object/struct/map with fields to override defaults. The fields required with this effort are:

• endpoint - the gRPC endpoint to use in format server:port. If required by the SDK, it should be reformatted internally to https://server:port.
• use_tls - boolean indicating if TLS should be used. Default value is true`

• Kotlin support
• Android (???version???) support

@michaeldboyd @tmarkovski , we need a sample application / large unit-test that consumes ProviderService so we can properly test it. Ideally, we have 100% coverage of all SDK endpoints.

• Sample application link sdk-examples repo
• How to download okapi native binaries
• Walkthrough of server and okapi

• --profile-default doesn't seem to be implemented. A new profile, when set with the command, doesn't change the default in config.toml

We need a build and test action for golang services.

• Release go okapi
• ?Package the okapi binaries? - NO, readme tells how to download
• ?Automatic download via python script (since golang is compiled)? - out of scope
• Unit test
• Release go services

Update every language

• C#
• Java #238
• Golang #239
• Node
• Web
• CLI
• Swift
• Python #236
• Ruby #241

• #244
• #245
• #251
• Golang on Ubuntu
• Golang on MacOS
• others?

Deliver SDKs in all possible languages - this ticket should be an epic

• Authentication/ Profile Management #27
• Wallet Service #27
• Provider Service #27
• Add additional Conceptual Docs
• JS references in walkthrough @michaeldboyd #46
• C# references in walkthrough @michaeldboyd #30
• Better walkthrough narrative @michaeldboyd #37
• onboarding page for how to get set up @michaeldboyd #37
• FAQ Technical Questions #37 @michaeldboyd

Discussion in slack channel.
https://app.slack.com/client/T01KP3XHJ68/C02C05JQC3Y/thread/C02C05JQC3Y-1632222814.003700

package main
​
import (
	"fmt"
​
	sdk "github.com/trinsic-id/sdk/go/proto"
	trinsic "github.com/trinsic-id/sdk/go/services"
)
​
const serviceAddress = "http://trinsic-staging.centralus.azurecontainer.io:5000/"
​
func main() {
	walletService, err := trinsic.CreateWalletService(serviceAddress, nil)
	if err != nil {
		panic(err)
	}
	fmt.Printf("%+v\n", walletService)
	wallet, err := walletService.CreateWallet("")
	if err != nil {
		fmt.Printf("%+v\n", err)
	} else {
		fmt.Printf("%+v\n", wallet)
	}
	providerService, err := trinsic.CreateProviderService(serviceAddress, nil)
	if err != nil {
		panic(err)
	}
	inviteResponse, err := providerService.InviteParticipant(&sdk.InviteRequest{
		Participant: sdk.ParticipantType_participant_type_individual,
		Description: "I dunno",
		ContactMethod: &sdk.InviteRequest_Email{
			Email: "[email protected]",
		},
	})
	if err != nil {
		panic(err)
	}
	fmt.Printf("%+v\n", inviteResponse)
}

Currently the Go SDK uses an internal context object for all remote calls. Among other things, this means users of the SDK can't specify a timeout or cancel a call to Trinsic.
#155

@tmarkovski @michaeldboyd It looks like newtonsoft is used/included by some of our nuget packages. Is there a reason to actually remove this?

Running "mkdocs" command complains that "tags" plugin is not installed. Installing the insiders version manually, fixes this.

• Package Support
  • Homebrew for Mac
  • Chocolatey for Windows
  • Cargo for Rustup
  • (descoped) apt-get for Linux

As a new user I can

• Follow steps to download a sample Android application with Trinsic's SDK added and get it running #220
• Follow steps on how to add Trinsic's java SDK to my Maven and/or Gradle toolchain in my project
• Follow steps to run a demo application that goes through the walkthrough

• https://github.com/trinsic-id/server/issues/184
• https://github.com/trinsic-id/server/issues/180
• https://github.com/trinsic-id/server/issues/182
• #95
• #96

golang doesn't allow duplicate structs anymore, so this is a required feature. I've manually edited the generated files, but we need to make the protoc code do it automatically.

• Okapi
• SDK

Content should include

• Intro line what this is
• Quick info to documentation
• Very quick getting CLI install info

Currently only Python is smart about this. We can extend to other languages easily

• Go
• Java
• C#
• Swift
• Python
• Objective C
• Ruby

A question about the intended use pattern of WalletService in the Go SDK. In a multi-wallet environment, a single WalletService is not thread-safe because in the below case

thread1:
  service.SetProfile(profileA)
  service.IssueCredential(documentA)
thread2:
  service.SetProfile(profileB)
  service.IssueCredential(documentB)

we can’t guarantee that each document is signed by the intended wallet.

In general this is an unusual pattern in Go, but assuming that’s necessary, the obvious solution is to create a WalletService for each wallet we’re working with.

However, from what I can see, each call to CreateWalletService creates a new gRPC connection, unless an existing *grpc.ClientConn is passed in. Creating a connection for each wallet object is not a great idea because it’s going to be very easy to reach a connection limit somewhere.

Is the intended use-pattern here to create a single *grpc.ClientConn and pass it to every call of CreateWalletService ?

Is there a reason why WalletService doesn’t take a WalletProfile for each API call? That would avoid the issue.

Also, under the hood, CreateChannelIfNeeded uses context.Background() (by calling grpc.Dial instead of accepting a context from the user and using grpc.DialContext which I’m not sure is a good idea in a library.

Describe the bug
npm sdk not building before getting released to npm.

To Reproduce
Steps to reproduce the behavior:

1. mkdir test-npm && cd test-npm; npm init && npm i @trinsic/trinsic
2. add const trinsic = require('@trinsic/trinsic'); to the top of the index.js
3. npm run
   notice how the module does not get imported. Inspecting the node_module shows that there is no ./dist directory
   

Expected behavior
build before publishing. successfully import
SDK (or CLI) you are using

• SDK: node

Additional context
Add any other context about the problem here or remove this section

Replace Ava with any framework that supports describe grouping.
Update tests in trust registry to use authenticated context and test wallet

Describe the bug
#156
Fails on http://20.75.134.127:80
We should allow parsing of IP addresses, not error out. We should still warn if we don't provide an explicit port.

Referring to the cli.yaml file, the register-egf command has not been implemented

• Java #164
• Golang (already done)
• Python #153
• Ruby #165
• Swift trinsic-id/sdk-swift#2
• C# - completed by @tmarkovski already
• Javascript

We need to handle golang errors better than just system panic for everything. Most will not be recoverable errors, but we should still allow the client to gracefully handle it.

• Okapi
• Services

• Okapi package
• SDK package
  https://www.youtube.com/watch?v=bkh0gPf4Noc&ab_channel=ComeUntoChrist.org

A generic error is thrown when trying to create a wallet with a security code from an invitation. I do receive the email with the same security code that is also in the inviteResponse.InvitationId. I have tried with the same provider wallet and also with a new provider wallet.

To Reproduce
Steps to reproduce the behavior:

Expected behavior
The wallet should be created for the user that has been invited without an error.

SDK (or CLI) you are using

• SDK: .NET
• Version: 1.0.1
• OS: Windows

Python - @michaeldboyd

• By Sept 20th - Documentation - update existing documentation with snippets, walkthrough additions and anything specific to Python that users should be directed #125
• By Sept 20th - Samples - provide basic usage for working with wallet and managing profiles. Use citizenship or vaccination vocabulary for sample credentials to work with. #125
• By Sept 20th - Reference server in Python
• Repl.it example

Verify android automotive is supported, at least the emulator.

This will help with consistency, as well as failing out the action as soon as one of the matrix os's fails.

• trinsic-id/okapi#197

Support react native on major platforms:

• MacOS
• Linux
• Windows
• Android
• iOS

https://docs.microsoft.com/en-us/azure/static-web-apps/authentication-custom?tabs=aad

Both our internal and external docs can be hosted on azure using their new static web apps option. this will give us:

• staging sites that build on PRs
• invitation only access with different identity providers

• Move all our repositories over to github
• Import all our bugs as issues
  This will need some level of automation, augmented by manual oversight. Ideally, the git repositories can be transferred using a second remote push --all. The issues will probably need some kind of migration using the Github API:
  https://docs.github.com/en/rest/reference/issues

C#

• repl.it app for demos
• Dogfood of C#
• Feedback on reference section
  JS
• reference app
• Dogfood of Javascript

• Okapi
• Services

Currently only .NET and Python do this.

• Java #178
• Go
• Ruby (https://brunosutic.com/blog/async-ruby)
• Swift (https://www.swiftbysundell.com/articles/connecting-async-await-with-other-swift-code)
• C#
• Python

• trinsic-id/okapi#187
• trinsic-id/okapi#191
• trinsic-id/okapi#194
• trinsic-id/okapi#195
• #145
• trinsic-id/okapi#193