docs: fix JWT auth recipe API errors from review feedback #81
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.
Corrects API mismatches in JWT authentication cookbook recipe based on code review feedback for PR #80.
JWT Claims Structure
exp: usizefield to Claims struct (JWT validation fails without it due tovalidate_exp: truedefault)expis optionalToken Creation
create_tokensignature: uses 2 parameters(claims, secret), not 3SystemTime::now()in login handlerexpin Claims before callingcreate_tokenFramework Consistency
#[tokio::main]→#[rustapi::main]to match other recipesJwtLayerinstantiation:JwtLayer::<Claims>::new(secret)with type parameter.with_algorithm()call (HS256 is default, use.with_validation()if customization needed)Minor Fixes
All changes align with actual
rustapi-extrasv0.1.233 implementation.💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.