fix: use id
insted of clientId
when generating the token
#666
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR changes/adds
Currently when generating a token for an
StsAccount
with theStsClientTokenGeneratorServiceImpl
theclient#clientId
property is used asparticipantContextId
passed to theParticipantSecureTokenService
. But when creating anStsAccount
in theStsAccountServiceImpl
theclientId
is sourced by theParticipantManifest#did
, which means thatThe
StsClientTokenGeneratorServiceImpl
works only if theparticipantContextId
is equals to thedid
of the participant.This fixes it by using the
id
instead ofclientId
of theStsAccount
Why it does that
Briefly state why the change was necessary.
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Who will sponsor this feature?
Please @-mention the committer that will sponsor your feature.
Linked Issue(s)
Closes # <-- insert Issue number if one exists
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.