Avoid exception when attempting to find member by Id when Id is not an expected Guid or integer, as can be the case with external member providers #18320
+14
−3
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.
Prerequisites
Resolves: #14713
Description
This PR applies a similar fix as #18078 for back-office members, where we want to be a bit more defensive about handling user Ids read from the HttpContext that may not be an expected integer or Guid, as can be the case with external member providers.
I don't have a test setup to reproduce this but I think visual inspection should suffice for reviewing this update.