-
Notifications
You must be signed in to change notification settings - Fork 1
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
Remove the user directory service api call from grant loader #60
Conversation
I still have local manual testing to perform, but I figured I'd open this now to start the review. |
Closing while making discussed changes to remove user dir api call all together since locatorIds are populated by User Service in Pass on user login. |
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.
Tests pass for me locally. The changes to user handling make logical sense and should speed things up a lot.
eclipse-pass/main#746
This PR has the following changes:
Removes the call to user directory api to get the HopkinsID for a user. Now if a User is created because it was not found in Pass, only the employeeId and jhed (eppn) locatorIds are created in the User. The HopkinsID (unique-id) locatorId will be inserted by the
ShibAuthenticationFilter
in thepass-core/pass-core-main
project when the user logs into Pass.Update the user locator ID logic that detects if locator IDs need to be updated. Now only the JHED ID is updated if it is different than what is in Pass.
Consolidated JhuPassUpdater and CoeusPassEntityUtil since JhuPassUpdater was very thin and the logic in CoeusPassEntityUtil is for updating Jhu Pass entities. This simplifies the code base.
Added grant difference logging for init mode so we know the changes that were made on grant so that data verification can be done.
Did some other general cleanup like removing methods in code base used only for testing.