FLP - Take withoutAuthorization Into Consideration When Checking For FLP
#3697
Conversation
This file contains 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
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.
Changes
This PR initially started by having the main FLP be aware of the Security's
isAuthorizationEnabledflag. But that revealed some other problems with FM/CMS, and then we decided not to do this change. But we'll want to tackle this ASAP.With this, in order to tackle the issue with the PB/Import Lambda function being blocked by FLP, we've added a way to disable FLP within that Lambda function. Once we resolve the discovered issue, we'll remove this functionality as it'll no longer be needed.
How Has This Been Tested?
Manually.
Documentation
N/A