https://github.com/shubhamharitash/jwt_login
JWT based login authentication system using spring security
https://github.com/shubhamharitash/jwt_login
jwt jwt-auth jwt-authentication jwt-authorization jwt-bearer-tokens jwt-decode jwt-token spring springsecurity springsecurity-jwt springsecurity-oauth2
Last synced: about 2 months ago
JSON representation
JWT based login authentication system using spring security
- Host: GitHub
- URL: https://github.com/shubhamharitash/jwt_login
- Owner: shubhamharitash
- Created: 2023-12-21T09:55:21.000Z (over 2 years ago)
- Default Branch: master
- Last Pushed: 2023-12-29T15:22:45.000Z (over 2 years ago)
- Last Synced: 2025-03-05T11:51:36.438Z (over 1 year ago)
- Topics: jwt, jwt-auth, jwt-authentication, jwt-authorization, jwt-bearer-tokens, jwt-decode, jwt-token, spring, springsecurity, springsecurity-jwt, springsecurity-oauth2
- Language: Java
- Homepage:
- Size: 69.3 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
Curious about how 𝗝𝗪𝗧 𝗔𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻 + 𝗦𝗽𝗿𝗶𝗻𝗴 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 works?
It's a three step process:
• Client hits a requests , which gets authenticated and a JWT token gets created using spring security prebuild encryptor and library along with some of our manual configs.
• Once JWT tokens (acces_token + refresh_token ) gets created they are send back to the UI which persist those tokens somewhere locally on client or preferably on servers.
• Then UI hits backs the request along with JWT token, and gets successfully served with the required API response.
This happens in fraction of time that it's not noticable to user.
These 2 above specified tokens namely access_token and refresh_token has limited lifespans , which is encrypted in the token itself.
lifespan of access_token<