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

feat: Add verify presentation API and update StatusList APIs [DEV-2811] & [DEV-2669] #265

Merged
merged 29 commits into from
Jul 7, 2023

Conversation

DaevMithran
Copy link
Contributor

@DaevMithran DaevMithran commented Jun 16, 2023

This PR includes the following

  • add /presentation/verify api
  • add /credential-status/create api
  • add /credential-status/update api
  • fix statusList creation and listing api's with latest did-provider-cheqd
  • updated swagger
  • fix external db bug, api guard is needed when external db is true even when auth is false
  • Added support for request body content type application/x-www-form-urlencoded
  • Supports did update operation in chunks

@Tweeddalex Tweeddalex changed the title feat: Init presentation feat: Add verify presentation API and other fixes [DEV-2811] Jun 20, 2023
@ankurdotb
Copy link
Contributor

@DaevMithran DaevMithran changed the title feat: Add verify presentation API and other fixes [DEV-2811] feat: Add verify presentation API and other fixes [DEV-2811] && [DEV-2669] Jun 26, 2023
@Tweeddalex Tweeddalex changed the title feat: Add verify presentation API and other fixes [DEV-2811] && [DEV-2669] feat: Add verify presentation API and other fixes [DEV-2811] & [DEV-2669] Jun 26, 2023
@Tweeddalex Tweeddalex changed the title feat: Add verify presentation API and other fixes [DEV-2811] & [DEV-2669] feat: Add verify presentation API and update StatusList APIs [DEV-2811] & [DEV-2669] Jun 26, 2023
Copy link
Contributor

@ankurdotb ankurdotb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Branch is not up-to-date with develop and has merge conflicts. (Note: this will always result in an instant rejection.)
  2. Can we please work through the Swagger file and agree on inputs/outputs? So for example I can see credential status and resource create both use a text input for DIDs and then the rest is just a body. Before we do this in code, can we agree on the changes in Swagger first and simplify? For example, for credential status create, I expect to see:
  • Issuer DID (text)
  • Status List Name (text)
  • Status Purpose (dropdown)
  • Encrypted (dropdown)
  • Options (optional, additional JSON for optional parameters)
    ...and so on for the other APIs. I at least want these for the credential service APIs, but would be good to do them for all and make it consistent as an approach.

@Tweeddalex Maybe for the scope of this, we do the simplifications for just presentation and credential status APIs, and then for next sprint do the implications and refactor for other APIs in a separate task.

src/app.ts Outdated Show resolved Hide resolved
src/app.ts Outdated Show resolved Hide resolved
Copy link
Contributor

@lampkin-diet lampkin-diet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No any new comments since previous review

@ankurdotb ankurdotb removed the request for review from lampkin-diet July 6, 2023 17:17
Copy link
Contributor

@ankurdotb ankurdotb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Status List API bits seem fine but Presentation verify confuses me in the response. There also seems to be stuff in here that's related to general API simplification on unrelated things like DIDs. See ClickUp comment and split

src/static/swagger.json Outdated Show resolved Hide resolved
src/static/swagger.json Outdated Show resolved Hide resolved
@ankurdotb ankurdotb merged commit 4e43430 into develop Jul 7, 2023
@ankurdotb ankurdotb deleted the presentation branch July 7, 2023 12:02
cheqd-bot bot pushed a commit that referenced this pull request Jul 7, 2023
## [2.4.0-develop.7](2.4.0-develop.6...2.4.0-develop.7) (2023-07-07)

### Features

* Add verify presentation API and update StatusList APIs [DEV-2811] & [DEV-2669] ([#265](#265)) ([4e43430](4e43430))
@cheqd-bot
Copy link

cheqd-bot bot commented Jul 7, 2023

🎉 This PR is included in version 2.4.0-develop.7 🎉

The release is available on:

Your semantic-release bot 📦🚀

cheqd-bot bot pushed a commit that referenced this pull request Jul 11, 2023
## [2.5.0-develop.1](2.4.1...2.5.0-develop.1) (2023-07-11)

### Features

* Add credential-status check API [DEV-2940] ([#293](#293)) ([34ad827](34ad827))
* Add Default role assigning while creating and account or signing in [DEV-2905] ([#286](#286)) ([c99bed2](c99bed2))
* Add verify presentation API and update StatusList APIs [DEV-2811] & [DEV-2669] ([#265](#265)) ([4e43430](4e43430))

### Bug Fixes

* Add policies to Verification API [DEV-2951] ([#294](#294)) ([d3c6ea9](d3c6ea9))
* Fix issue with broken webhook being used for setting default user role in LogTo [DEV-2962] ([#295](#295)) ([a3c8fde](a3c8fde))
@cheqd-bot
Copy link

cheqd-bot bot commented Jul 11, 2023

🎉 This PR is included in version 2.5.0-develop.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

cheqd-bot bot pushed a commit that referenced this pull request Jul 11, 2023
## [2.5.0](2.4.1...2.5.0) (2023-07-11)

### Features

* Add credential-status check API [DEV-2940] ([#293](#293)) ([34ad827](34ad827))
* Add Default role assigning while creating and account or signing in [DEV-2905] ([#286](#286)) ([c99bed2](c99bed2))
* Add verify presentation API and update StatusList APIs [DEV-2811] & [DEV-2669] ([#265](#265)) ([4e43430](4e43430))

### Bug Fixes

* Add policies to Verification API [DEV-2951] ([#294](#294)) ([d3c6ea9](d3c6ea9))
* Fix issue with broken webhook being used for setting default user role in LogTo [DEV-2962] ([#295](#295)) ([a3c8fde](a3c8fde))
@cheqd-bot
Copy link

cheqd-bot bot commented Jul 11, 2023

🎉 This PR is included in version 2.5.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@cheqd-bot cheqd-bot bot added the released label Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

4 participants