Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fixes copy in jwt blog #169

Merged
merged 1 commit into from
Aug 8, 2023
Merged

fixes copy in jwt blog #169

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/what-is-jwt/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,8 +74,8 @@ You may have noticed that in the JWT (that is issued by Google) example above, t
- **at_hash**: The hash of the access token. The OAuth access token is different from the JWT in the sense that it’s an opaque token. The access token’s purpose is so that the client application can query Google to ask for more information about the signed in user.
- **email**: The end user’s email ID
- **email_verified**: Whether or not the user has verified their email.
- **iat**: The time (in milliseconds since epoch) the JWT was created
- **exp**: The time (in milliseconds since epoch) the JWT was created
- **iat**: The time (in milliseconds since epoch) the JWT was created.
- **exp**: The time (in milliseconds since epoch) the JWT will expire.
- **nonce**: Can be used by the client application to prevent replay attacks.
- **hd**: The hosted G Suite domain of the user

Expand Down
Loading