VC-AuthN Monitoring
Open
theme:vc-authn
- Dominant language
- Shell
- Stars
- 2
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
There is a need to monitor the success/failure rates of authentication events going through VC-AuthN and to determine what the root cause of authentication failures is (i.e.: intermittent authentication failure with proof-requests that do not have a valid proof of non-revocation).
Related to https://github.com/openwallet-foundation/acapy-vc-authn-oidc/issues/833
Contributor guide
Research direction
Start by reading the related acapy-vc-authn-oidc issue 833 and tracing the VC-AuthN authentication-event path described here. Define how success and failure rates should be monitored and how failures involving proof requests without valid proof of non-revocation will be identified and reported.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100