When a user logs in, Spring Security verifies their credentials. Once authenticated, instead of creating a server-side session, Spring Security generates a JWT containing information about the user (claims like username, roles, etc.). This JWT is then signed with a secret key known only to the server.
active 2023-10-25 → 2023-10-26 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 2 days from 2023-10-25 to 2023-10-26. Pushes: 1 total, peak 1 in a day. Pull requests: 2 total, peak 2 in a day. Issues: 0 total, peak 0 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| Anshika-Pal | 2 | 1 | 1 | 0 |
| DevShivmohan | 1 | 0 | 1 | 0 |
Recent activity
Latest issues, pull requests and releases
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 0 stars here means stars gained during the window, not the repo's star count.