Implement token endpoints for auth-service #38
Labels
No labels
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Support
Type
Task
Type
Testing
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Blocks
Depends on
You do not have permission to read 1 dependency
#42 Implement token endpoints
clevermicro/user-management
Reference: clevermicro/user-management#38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
According to this design document: https://wiki.cleverthis.com/en/architecture/microservices/feature-discussion/im-endpoints, this ticket should implement the following endpoints within the
token-service-v1
:verifyAccessToken(accessToken: String, checkLiveness: Boolean)
cleverthis.clevermicro.invalid_access_token
exception.checkLiveness=true
will cause the auth service to call keycloak to check if the token is still alive (aka not revoked due to log out or account disabled).getClientToken(clientId: String, clientSecret: String): TokenResp
refreshToken(refreshToken: String): TokenResp
Get token with refresh token, can be used for both client service account and user accounts, although for now it's mainly for client service accountsclient_credentials
does not return a refresh token based on this rfc: https://datatracker.ietf.org/doc/html/rfc6749#section-4.4.3The token-service-v1 does not require any authorization. The unit tests are included in this ticket.