Fix handling of auth scheme/strategy realms #4281
Merged
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.
We were seeing some hard-to-explain behavior in #4218 as it relates to the realm of the
server
inside of auth schemes. In short, each timeserver
is cloned, all servers were being mutated such thatserver.auth.strategy
was bound to the server of the most recent clone.Cloning is the process by which hapi creates independent realms for a. each plugin and b. each auth strategy. When
server
is cloned, the clone'srealm.parent
is assigned toserver.realm
. Due to the mutation of a shared interface during each clone, theserver.realm
within an auth strategy had a strange/unpredictable chain of ancestor realms. This work tidies that up by no longer mutating the sharedauth
on each clone, instead creating a new public auth interface for each one.Resolves #4218.