-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature/Identity] User operations: create update delete #4741
[Feature/Identity] User operations: create update delete #4741
Conversation
71a29f3
to
33e8d47
Compare
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
33e8d47
to
56db04e
Compare
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Codecov Report
@@ Coverage Diff @@
## feature/identity #4741 +/- ##
======================================================
- Coverage 70.64% 70.50% -0.14%
+ Complexity 57685 57631 -54
======================================================
Files 4675 4680 +5
Lines 277347 277478 +131
Branches 40556 40562 +6
======================================================
- Hits 195935 195642 -293
- Misses 64951 65428 +477
+ Partials 16461 16408 -53
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
import java.util.Map; | ||
|
||
public class User { | ||
public class User implements Subject { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think User should be a subject since its (de)serialized, I think we should have a sperate InternalSubject that references an instance of User, what do you think of this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might be a bit confused here. In my understanding, a User is one of the many types of Subject, and InternalSubject and Subject were same. Let me know if my understanding is correct.
Also, w.r.t. serialization/deserialization, isn't the PrincipalIdentifierToken the only serializable entity? Correct me if my understanding is off
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
User represents the storage medium, Subject has functionality built onto it, and while the principal has strong alignment with the user, I would recommend we create another class to be a Subject that can swap out which User principal is pointed to. Take a look at Shiros tutorial [1], its usage mirrors closely what I think we should implement here. What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
okay..makes sense... I will update this PR accordingly
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
29a76be
to
808eea8
Compare
Gradle Check (Jenkins) Run Completed with:
|
Precommit task
Similar reason for Check task
|
Gradle Check (Jenkins) Run Completed with:
|
Gradle Check (Jenkins) Run Completed with:
|
Signed-off-by: Craig Perkins <cwperx@amazon.com>
… those operations Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
… as adds a couple of tests Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
… realm itself Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
Signed-off-by: Darshit Chanpura <dchanp@amazon.com>
e4fee4b
to
13034d1
Compare
Gradle Check (Jenkins) Run Completed with:
|
The latest commit e10c925 on main experienced same test failure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lets merge this so we can build a Rest API action to create a user end to end. Flip it to draft and we can see about merging
We can merge this. I'll create a follow-up PR to add rest API for createUser functionality |
Signed-off-by: Darshit Chanpura dchanp@amazon.com
Description
Adds C, U, D operations for internal user in an in-memory store.
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.