-
Notifications
You must be signed in to change notification settings - Fork 11
Store user data in request #244
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b39ba6e to
0b75c4d
Compare
bryank-cs
reviewed
Jun 7, 2025
Collaborator
Author
|
closes #240 |
021a1af to
969c0ad
Compare
This reverts commit 2966ded.
6ae8f39 to
5bb021b
Compare
af10183 to
d3c1e2e
Compare
This was referenced Jun 16, 2025
Draft
bryank-cs
approved these changes
Jun 17, 2025
bryank-cs
approved these changes
Jun 17, 2025
Collaborator
Author
Collaborator
Author
simonLeary42
added a commit
that referenced
this pull request
Nov 10, 2025
* prevent access to user attributes when they might not be defined * getuid without existing is OK * store attributes in request * replace bad variable name (#242) * email -> mail * use new vars * fix request fetch * fix tests * add function getOrgMemberUIDs, copied from UnityGroup * fix inOrg (#245) * rename variable * use email from request * fix tests * remove extra space * rewrite tests * fix tests * fix tests * fix tests * fix test * remove prune * remove old comment * more similar to previous revision * wording * consistent * Revert "more similar to previous revision" This reverts commit 2966ded. * delete org before user * flush redis cache in tests * absolute exception * fix requestExists * remove redundant assertions remove unused variable (#269) fix error in UnityGroup->denyRequest fix missing email in denyGroup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem:
When redis is flushed, the names/emails/orgs of all nonexistent users disappear. Any attempt to approve requests made by these users will result in a white screen of death because the portal doesn't know what name/email/org to write to LDAP.
Solution:
Any access to name/email/org for a nonexistent user is now an error. name/email/org are stored with each request.
Notes:
The request creations now have assertions that
$USERand$SSOmatch. This is to prevent an admin from viewing as another user and accidentally submitting a request for that user with the admin's name/email/org.