Implement Access Enforcement point in CleverMicro #13
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 milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Depends on
You do not have permission to read 3 dependencies
Reference: clevermicro/user-management#13
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?
Ref epic: #103
CleverMicro shall implement an Access Enforcement point, where it will ensure that:
1.1 - implement JWT verification logic - token validity and subject match
1.2 - implement /login endpoint allowing client to obtain valid JWT token after providing valid credentials
1.3 - implement a microservice that will allow permission management
2.1 design the user permissions system
2.2 design the user permission actual implementation (choose storage solution, schema design, entity representation, and document the design details)
2.3 implement the actual user permission, and define/implement access / CRUD queries that will allow request authorisation and permission management
Closing Epic as it has been split and recreated in the correct Repo