Refresh Token Support and package refactor based on best practice docs #18
jtom38
commented 2024-04-21 10:30:37 -07:00
Owner
No description provided.
jtom38
added 15 commits 2024-04-21 10:30:38 -07:00
moved away from the api directory to internal per go doc recommendations
a2e740eefd
moved main.go to cmd folder per best practice
439c8ed733
updated how refresh token service and repo work
f5eea08c1e
added a interface for userService
8d8781eac4
updated pathing in main and updated how to find migrations
029710ad31
Moved entity id's to int64 that the sql driver returns
5b2ff607b9
Updated some responses to return the base struct with embedding
e218da5e7d
added RefreshTokenRequest as a body
0383d554b8
Moved handler to use interfaces and added the refreshToken endpoint
b02ed3f86a
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
e7f706b6e7
small improvement to creating a jwt logic
8482afed8d
auth handler now can work with refresh token request
be337b4bb9
minor changes to requests and responses
9627c51e7a
uuid was added
26820d80f7
small helper file updates
7d6e7d46cd
jtom38
merged commit 13d6e33b72 into main 2024-04-21 10:30:52 -07:00
jtom38
deleted branch features/restructure-go-recommendations 2024-04-21 10:30:52 -07:00
jtom38
referenced this issue from a commit 2024-04-21 10:30:53 -07:00
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
Block a user
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?