updated vc removal from community to extend auth policy with account host credentials in memory #4181
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.
This PR enables the mutation on the server to run,. key here is that the authorization policy has to be extended in memory, based on the information from the incoming request. This is similar to how user self removal works.
In addition the authorization policy around account / space has been tidied up, with the result that the VC provider will now have the GRANT privilege + so will see the button to leave.
Other updates:
removed CREATE_DISCUSSION privilege assignment from community;
trigger authorization reset after assign license plan to account;
removed spaceIngest mutation that logically should not be there