Avoids collection was modified issue when flowing identities to the authenticated user's principal #18527
+7
−1
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
…uthenticated user's principal.
nikolajlauridsen
approved these changes
Mar 4, 2025
|
Let's do that - I have verified it locally with IIS. |
AndyButland
deleted the
v13/bugfix/fix-issue-with-iis-basic-auth-and-backoffice-login
branch
AndyButland
added a commit
that referenced
this pull request
Mar 12, 2025
…uthenticated user's principal. (#18527)
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.
Prerequisites
Resolves: #18509
Description
It looks as if #18206 introduced an issue in this situation, where you have a user authenticated via IIS basic authentication before attempting to sign-in to the backoffice.
I haven't been able to reproduce it using the public access feature on Umbraco Cloud.
I've been able to reproduce locally: #18509 (comment) - so these are the test steps.
When I try this process again with the code from this PR in place, I no longer see the issue.