aries-rfcs icon indicating copy to clipboard operation
aries-rfcs copied to clipboard

Published 20 hours ago • verified publisher icon hyperledger

"present-proof" does not specify rejection problem report code

Open devin-fisher opened this issue 4 years ago • 1 comments

Working on "present-proof" for Aries Interop Profile 1.0. The current RFC does not really describe how rejection happens. "issue-credential" provides hints, it specifies the use problem-report message. I'm assuming that "present-proof" works the same way. But neither specify how that happens. It would seem that the RFC must specify what problem-report.description.code leads to rejection.

We could specify a generic reject code for any need rejection use cases or We could specify specific codes (eg. reject-presentation-request)

How are other implementers handling this issue? I'm I missing something?

devin-fisher avatar Apr 28 '20 22:04 devin-fisher

@andrewwhitehead @tmarkovski @CHempel-esatus - comments on this question?

swcurran avatar May 01 '20 14:05 swcurran