Refresh Token Support and package refactor based on best practice docs #18
jtom38
commented
Owner
No description provided.
jtom38
added 15 commits 2024-04-21 10:30:38 -07:00
a2e740eefd
moved away from the api directory to internal per go doc recommendations
439c8ed733
moved main.go to cmd folder per best practice
f5eea08c1e
updated how refresh token service and repo work
8d8781eac4
added a interface for userService
029710ad31
updated pathing in main and updated how to find migrations
5b2ff607b9
Moved entity id's to int64 that the sql driver returns
e218da5e7d
Updated some responses to return the base struct with embedding
0383d554b8
added RefreshTokenRequest as a body
b02ed3f86a
Moved handler to use interfaces and added the refreshToken endpoint
e7f706b6e7
The refreshtoken no longer cares about when a token expired. When they want a new jtw from refresh a new refresh token is made also
8482afed8d
small improvement to creating a jwt logic
be337b4bb9
auth handler now can work with refresh token request
9627c51e7a
minor changes to requests and responses
26820d80f7
uuid was added
7d6e7d46cd
small helper file updates
jtom38
merged commit 13d6e33b72 into main
jtom38
deleted branch features/restructure-go-recommendations
jtom38
referenced this issue from a commit
Merge pull request 'Refresh Token Support and package refactor based on best practice docs' (#18) from features/restructure-go-recommendations into main
Loading…
Reference in New Issue
No description provided.
Delete Branch "features/restructure-go-recommendations"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?