-
Notifications
You must be signed in to change notification settings - Fork 2
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
Allow multiple wallets per subject #213
Conversation
@@ -154,7 +154,8 @@ public async Task Verify_OnlySingleAllowedPerSubject() | |||
_options, | |||
new CreateWalletRequest()); | |||
|
|||
firstCreateResult.Result.Should().BeOfType<CreatedResult>(); | |||
var firstResponse = firstCreateResult.Result.Should().BeOfType<CreatedResult>() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not spin it up and call via rest?
|
||
var sliceDb = await _certRepository.GetOwnersAvailableSlices(registry, slice.CertificateId, wallet1.Owner); | ||
|
||
sliceDb.Should().HaveCount(1); | ||
sliceDb.Should().ContainEquivalentOf(slice); | ||
} | ||
|
||
[Fact] | ||
public async Task QueryAvailableCertificates_MultipleWallets() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this desired? Do we wan't to sum over wallets when querying certificates?
Quality Gate passedIssues Measures |
This adds support for a subject/user in the wallet to create multiple wallets.
All query apis returns results for the subject and not on an individual wallet level.
This is a precursor of future implementations which will enable a user to delegate access to a specific wallet to other users.