feat: consistent response return between local and jwt strategy #2042
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.
Currently, when /authentication service is trigger with
local
strategy, it is missingauthentication.accessToken
andauthentication.payload
field as compared tojwt
strategyThis commit attempts to ensure consistency in both response
I added in
authentication
package instead ofauthentication-local
becausejsonwebtoken
is already available and it seem like the correct place to add