-
Notifications
You must be signed in to change notification settings - Fork 340
Description
NOTE: #2567 must be merged before this is actionable.
In order to implement Service Accounts (#2597), we need the Security Plugin to be able to vend an authorization token back to core.
When core requests a Service Account for an extension (#2609), the response from the Security Plugin should include an authorization token associated with the Service Account. The authorization token can be made using the token generator introduced in #2567. This should provide the framework for creating a JWT that can be passed back to core and then later verified by the Security Plugin.
The authorization token should correspond to the Service Account associated with the extensionId that core provides. This PR should be straightforward to implement since the framework for generating a JWT is already introduced.
This issue will be complete when there is a PR that takes in an extensionUniqueId, fetches the corresponding Service Account from the Internal Users Storage, and finally creates a JWT based on this information. The final PR should contain tests that show that a JWT is created from an arbitrary string (representing the ID) and that this token can later be verified.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status