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

Does the approach taken in §8.1 change if issuer == named actor? #163

Closed
scouten-adobe opened this issue Aug 5, 2024 · 1 comment
Closed
Assignees
Milestone

Comments

@scouten-adobe
Copy link
Contributor

Review the credential described in §8.1. Though not common in practice today, a named actor could be issued a VC with its own document signing capability. In that case, the named actor might want to directly sign the creator identity assertion themselves (i.e. serve a dual role as named actor + issuer) rather than having their identity presented by a third-party identity assertion generator.

If so, is the approach taken in §8.1 still valid? If not, how should we adapt?

@scouten-adobe scouten-adobe added this to the 1.x-add-w3c-vc milestone Aug 5, 2024
@scouten-adobe scouten-adobe self-assigned this Aug 5, 2024
@scouten-adobe
Copy link
Contributor Author

Closing. §8.1 no longer supports self-signing. Will reconsider when/if we do support autonomous signing.

@scouten-adobe scouten-adobe reopened this Sep 10, 2024
@scouten-adobe scouten-adobe closed this as not planned Won't fix, can't repro, duplicate, stale Sep 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant