clevermicro/user-management
clevermicro/user-management
14
0
Fork 0
Code Issues 9 Pull requests Projects Releases Packages 1 Wiki Activity Actions

Refactor auth-service /auth Endpoint for UMA-Based Authorization #28

New issue
Closed
opened 2025-06-03 23:06:43 +00:00 by abed.alrahman · 0 comments
abed.alrahman commented 2025-06-03 23:06:43 +00:00
Member
Copy link

Goal: Modify the /auth endpoint in auth-service to perform endpoint authorization by making UMA (User-Managed Access) permission evaluation requests to Keycloak, instead of checking for pre-defined client roles.
Brief Description: The /auth endpoint, used by Traefik for forward authentication, needs to be updated. When a request comes for a backend service, /auth will:

Validate the user's token.
Identify the target backend service (which acts as a Keycloak Resource Server), the specific resource (API path), and the scope (HTTP method) being accessed.
Make a permission evaluation request (e.g., by requesting an RPT or using the UMA evaluation endpoint) to Keycloak against the target service's Resource Server configuration.
Respond 200 OK (with user metadata headers) to Traefik if Keycloak grants permission, or 401/403 if denied. This requires auth-service to be configured to understand how to map incoming requests to Keycloak resources/scopes defined by backend services.
Goal: Modify the /auth endpoint in auth-service to perform endpoint authorization by making UMA (User-Managed Access) permission evaluation requests to Keycloak, instead of checking for pre-defined client roles. Brief Description: The /auth endpoint, used by Traefik for forward authentication, needs to be updated. When a request comes for a backend service, /auth will: Validate the user's token. Identify the target backend service (which acts as a Keycloak Resource Server), the specific resource (API path), and the scope (HTTP method) being accessed. Make a permission evaluation request (e.g., by requesting an RPT or using the UMA evaluation endpoint) to Keycloak against the target service's Resource Server configuration. Respond 200 OK (with user metadata headers) to Traefik if Keycloak grants permission, or 401/403 if denied. This requires auth-service to be configured to understand how to map incoming requests to Keycloak resources/scopes defined by backend services.
abed.alrahman added this to the V.01 milestone 2025-06-04 10:29:48 +00:00
hurui200320 added reference feat/28 2025-06-16 06:44:36 +00:00
hurui200320 2025-06-30 09:05:21 +00:00
Sign in to join this conversation.
feat/28
Branches Tags
Clear current reference
master
feat/43
feat/authz-scaffolding
develop
Clear current reference
No results found.
Labels
Clear labels
  
Blocked

A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
Should have feature in order to satisfy the epic/legendary.

  
Needs feedback

There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
1 man-hours worth of work for an expert with no learning curve.

  
Points
13
13 man-hours worth of work for an expert with no learning curve.

  
Points
2
2 man-hours worth of work for an expert with no learning curve.

  
Points
21
21 man-hours worth of work for an expert with no learning curve.

  
Points
3
3 man-hours worth of work for an expert with no learning curve.

  
Points
34
34 man-hours worth of work for an expert with no learning curve.

  
Points
5
5 man-hours worth of work for an expert with no learning curve.

  
Points
55
55 man-hours worth of work for an expert with no learning curve.

  
Points
8
8 man-hours worth of work for an expert with no learning curve.

  
Points
88
88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
This ticket has backlogged priority and is not to be worked on yet

  
Priority
Critical
The priority is critical

  
Priority
High
The priority is high

  
Priority
Low
The priority is low

  
Priority
Medium
The priority is medium

  
Signed-off: Owner

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead

When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike

A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
A ticket that represents the same content as an existing ticket.

  
State
In Progress
A ticket that is actively being developed.

  
State
In Review
A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Bug
Something that doesnt work as intended.

  
Type
Discussion
Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
An error or improvement needed in the documentation.

  
Type
Epic
Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
Some new functionality not present.

  
Type
Legendary
A type of Epic which will contain other Epics.

  
Type
Support
Someone needs help using the project.

  
Type
Task
A generic task that doesnt fit into the other type categories.

  
Type
Testing
Work exclusively focusing on fixing or expanding testing.

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
Milestone
Clear milestone
No items
No milestone
V.01
Projects
Clear projects
No items
No project
Sprint June 1st- 14th
Assignees
Clear assignees
No assignees
hurui200320
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on
#9 Design the Group/Tenant Feature
clevermicro/user-management
#31 Implement UMA ticket for forward-auth
clevermicro/user-management
Reference: clevermicro/user-management#28
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?