Fixed Cookie Timeout Lookup Values#6814
Merged
bdukes merged 1 commit intoDec 2, 2025
Merged
Conversation
vmasanas
reviewed
Nov 27, 2025
bdukes
force-pushed
the
feature/fix-cookie-persistence-6811
branch
from
December 2, 2025 20:44
162499f to
63a8c2b
Compare
bdukes
approved these changes
Dec 2, 2025
The existing behavior blindly assumed that if a location node exists that the system.web.authencation/forms element is in the location node. This updates the behavior to start with the normal location, IF if funds forms authenticaton it continues, otherwise, it tries to find it under a location node IF location nodes exist. This should restore functionality after the updates recently resulted in ALL installations having a location node. This has been tested and appears to be working well
bdukes
force-pushed
the
feature/fix-cookie-persistence-6811
branch
from
December 2, 2025 20:45
63a8c2b to
74424c3
Compare
bdukes
enabled auto-merge (rebase)
December 2, 2025 21:00
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Summary
The existing behavior blindly assumed that if a location node exists that the system.web.authencation/forms element is in the location node.
This updates the behavior to start with the normal location, IF if funds forms authenticaton it continues, otherwise, it tries to find it under a location node IF location nodes exist.
This should restore functionality after the updates recently resulted in ALL installations having a location node. This has been tested and appears to be working well