Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize Verification across the SDKS and the Agent #111

Open
elribonazo opened this issue Jan 24, 2025 · 0 comments
Open

Standardize Verification across the SDKS and the Agent #111

elribonazo opened this issue Jan 24, 2025 · 0 comments
Labels
Commited Commitment to deliver in the current PI type:roadmap This issue will appear in the [project roadmap](https://github.com/orgs/hyperledger/projects/48)

Comments

@elribonazo
Copy link
Contributor

Short Description

Verification on Identus is using different protocols (to ask a holder to verify some claims on his credentials) We currently use 2 different verification flows or specifications. To reduce the maintenance cost, and make our products easier to use and understand we should have a single speciification across all our stack. This basically requires the cloud agent to implement Presentation exchange protocol V2 and deprecate the old one.

Sdks will then have to deprecate the old one.

We will try to avoid breaking changes at all cost by giving the users 2 releases of margin to upgrade.

Value statement

Code is cheaper to maintain and more interoperable with other identity solutions by removing duplicate functionality (Presentation exchange protocol  VS existing Verification protocols)  and (prism-jwt VS jwt specification)

Components

Cloud Agent
SDKS

Team members

@hyperledger/identus-maintainers

Architect

@hyperledger/identus-maintainers

QA Member

@hyperledger/identus-maintainers

Owner

@hyperledger/identus-maintainers

@elribonazo elribonazo added the type:roadmap This issue will appear in the [project roadmap](https://github.com/orgs/hyperledger/projects/48) label Jan 24, 2025
@elribonazo elribonazo added the Commited Commitment to deliver in the current PI label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Commited Commitment to deliver in the current PI type:roadmap This issue will appear in the [project roadmap](https://github.com/orgs/hyperledger/projects/48)
Projects
Development

No branches or pull requests

1 participant