search

peppelinux / draft-demarco-oauth-status-assertions

OAuth 2.0 Status Assertions for Digital Credentials
Other
4 stars 4 forks source link

Extended Error Codes PR #45

Closed SaraConsoliACN closed 1 month ago

SaraConsoliACN commented 1 month ago

This PR aims to resolve issue #14.

peppelinux commented 1 month ago

pleaser close this PR and revamp it according the structure proposed here: https://github.com/peppelinux/draft-demarco-oauth-status-attestations/pull/37/files#diff-6018989306b8996e79d471eb123fc3b59796d1635384b6faac8cdb36cd5f49ccR453

marinaado commented 1 month ago

Right know, we have two sections describing errors- one in the Assertion Request chapter and second in the Assertion Response chapter. There are two types of errors also, one for bad request and second for invalid credential. I would suggest to move all the text about the errors to the Assertion Response chapter as we are talking about how to construct response in the case of one of these two errors. Then we can consolidate the text. Perhaps this is a separate PR. I can make it if we agree it is a good idea.

peppelinux commented 1 month ago

@marinaado we can find an editorial solution for this, at the current stage the status_assertion_responses is returned with both success or errors, since the request is made for several assertions where all or only part of these may raise errors