Added Code Hints to custom-session-jwt example Implementation #8936
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.
After Encountering a limitation With Http Only Cookies and Safari, i decided to switch Over to Jwt Session Strategy.
Followed The Approach provided in the example code here custom-session-jwt example.
The Example Had the token Signed Manually as shown below
keystone/examples/custom-session-jwt/keystone.ts
Lines 88 to 99 in 4e1cf3f
Spent a whole day trying to figure out where to generate the token for the
authenticateWithPassword
mutation to work right.Finally cracked it by delving into the
statelessSessions
implementation code. Turns out, the sessionStrategy Start Method should return the signed Token.Suggest adding a hint in the example to save newcomers like me the trouble of digging deep.